Public bug reported:
I'm using LVM for all my linux partitions except /boot. They include /,
/home, swap, and /var, all formated with reiserfs. By "corrupt", I mean
some of the LVs fail to pass fsck and can not be repaired even with
--rebuild-tree. On a Hardy beta, to make the problem show up, you need
the following conditions:
1. Use the partition scheme described above.
2. Make sure directory /var/log/fsck doesn't exist on the root partition, which
is the case when installing a new system using the above partition scheme.
3. Boot with usplash on, i.e. do a normal boot.
The root of the problem is line 86 in /etc/init.d/checkfs.sh:
logsave -s $FSCK_LOGFILE fsck -C3 -R -A $fix $force $FSCKTYPES_OPT
3>$PROGRESS_FILE &
With the above conditions, logsave will try to buffer the output of fsck and
later save it in the /var partition. And this single line will corrupt some of
my LVs. I think something evil is going on here, about the output redirection,
because the problem goes away if I change the line into
fsck -C3 -R -A $fix $force $FSCKTYPES_OPT 3>$PROGRESS_FILE | logsave -s
$FSCK_LOGFILE - &
The same problem may also exist in /etc/init.d/checkroot.sh, with the
same line of script. It doesn't trouble me because in checkroot.sh this
line is only executed when your root partition is formated with ext2/3.
(Mine is reiserfs)
** Affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
--
checkfs.sh corrupts my LVM logical volumes when /var is on a separate partition
(Hardy beta)
https://bugs.launchpad.net/bugs/211417
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
