From: jmerkey <jmerkey@utah-nac.org>
To: Valdis.Kletnieks@vt.edu
Cc: Al Viro <viro@ftp.linux.org.uk>,
Linus Torvalds <torvalds@osdl.org>,
"Paolo 'Blaisorblade' Giarrusso" <blaisorblade@yahoo.it>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix ext3 warning for unused var
Date: Sun, 09 Oct 2005 16:47:44 -0600 [thread overview]
Message-ID: <43499E10.8060502@utah-nac.org> (raw)
In-Reply-To: <200510092358.j99NwlQj021703@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu 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
next prev parent reply other threads:[~2005-10-10 0:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 19:58 [PATCH] Fix ext3 warning for unused var Paolo 'Blaisorblade' Giarrusso
2005-10-09 20:16 ` Linus Torvalds
2005-10-09 19:53 ` jmerkey
2005-10-09 21:29 ` Al Viro
2005-10-09 20:18 ` jmerkey
2005-10-09 22:08 ` Al Viro
2005-10-09 22:13 ` jmerkey
2005-10-09 23:47 ` Al Viro
2005-10-09 23:55 ` Valdis.Kletnieks
2005-10-10 1:43 ` Gene Heskett
2005-10-09 23:58 ` Valdis.Kletnieks
2005-10-09 22:47 ` jmerkey [this message]
2005-10-10 11:02 ` Andi Kleen
2005-10-28 18:23 ` Peter Osterlund
-- strict thread matches above, loose matches on Subject: below --
2005-10-06 15:35 Paolo 'Blaisorblade' Giarrusso
2005-09-29 18:40 Paolo 'Blaisorblade' Giarrusso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43499E10.8060502@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.