[email protected] wrote:
On Sun, 09 Oct 2005 23:08:38 BST, Al Viro said:
Since when does fsck run fsck.ext3 on filesystems that are not marked
as ext3 in /etc/fstab?
Part of the problem is that if a partition is formatted with mkfs.ext3,
it gets an ext3 magic number scribbled at a known offset into the partition.
If you then reformat it with mkfs.reiserfs, that scribbles a different
magic number elsewhere on the partition, but leaves the ext3 magic number
intact. As a result, if you forget to update /etc/fstab, fsck.ext3 checks
for its magic number, finds it, concludes it's probably an ext3, and then
discovers that everything is totally scrogged.....
Yes, it's pilot error, but it's definitely hitting your feet with much larger
caliber rounds than you would have expected... :)
Yep. Needs to get fixed because when you upgrade from a reiserfs
system and try to keep the reiserfs partitions and add a new hard drive
(+1) to
an existing system, you run the risk of corrupting resiferfs partitions.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
