After testing this new patch on 2.4.10 I have detected a problem when trying
to convert mounted partitions to ext3.
The problem is that on umounting the partition, with 2.4.10 kernel, the
has_journal feature mark is removed, so the device is not detected as having
journal on next mount.
Creating journals (converting to ext3) on partitions that are not mounted
works ok.
Following is a practical demonstration of this in case I didn't explain
myself well...
pul:/# grep var /etc/fstab
/dev/hda7 /var auto rw 0 2
pul:/# mount|grep var
/dev/hda7 on /var type ext2 (rw)
pul:~# tune2fs -l /dev/hda7|grep -i journal
pul:~# ls -l /var/.journal
ls: /var/.journal: No such file or directory
pul:~# tune2fs -j /dev/hda7
tune2fs 1.24a (02-Sep-2001)
Creating journal inode: done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
pul:~# tune2fs -l /dev/hda7|grep -i journal
Filesystem features: has_journal filetype sparse_super
Journal UUID: <none>
Journal inode: 12
Journal device: 0x0000
pul:~# ls -l /var/.journal
-rw------- 1 root root 8388608 sep 24 13:39 /var/.journal
pul:/# umount /var
pul:/# tune2fs -l /dev/hda7|grep -i journal
pul:/# mount /var
pul:/# mount|grep var
/dev/hda7 on /var type ext2 (rw)
pul:/# ls -l /var/.journal
-rw------- 1 root root 8388608 Sep 24 13:39 /var/.journal
Regards...
-- Manty/BestiaTester -> http://manty.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/