Red Hat Bugzilla – Bug 98310
up2date causes corrupt filesystem
Last modified: 2007-11-30 17:06:53 EST
Description of problem:
I did a full up2date on AS 2.1 to 2.4.9-e.25smp. When I rebooted the box, /var
was mounted twice on my box as a normal partition and also as a raw partition:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/md2 8254200 2809000 5025908 36% /
/dev/md1 101018 33055 62747 35% /boot
none 513860 0 513860 0% /dev/shm
/dev/md3 7076060 3110388 3606224 47% /var
/dev/sda3 7076060 3110388 3606224 47% /var
This led to severe corruption of my filesystem.
Phil D'Amore helped me fix this issue by modifying /etc/fstab and replacing
Version-Release number of selected component (if applicable):
Always (I up2dated 3 boxes and had this corruption issue on all 3)
Steps to Reproduce:
1. up2date system with separate /var partition
df shows /var mounted twice, filesystem corruption
/var mounted once, no filesystem corruption =p
I dont really see how this is an up2date issue?
File system corruption is more or less always a
kernel issue, and up2date doesnt touch fstab. It's
possible one of the packages in the transaction
set may of had problems.
What about this case of filesystem corruption
makes it appear to be a up2date issue?