From: jmerkey <jmerkey@utah-nac.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: 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:13:51 -0600 [thread overview]
Message-ID: <4349961F.7060109@utah-nac.org> (raw)
In-Reply-To: <20051009220838.GN7992@ftp.linux.org.uk>
Al Viro wrote:
>On Sun, Oct 09, 2005 at 02:18:17PM -0600, jmerkey wrote:
>
>
>>If they all use the same on disk formats as their basic structure,
>>
>>
>
>ext3 and reiserfs? No, they do not.
>
>
>
>>fsck
>>should not return gt > 1 due to misinterpreting reiser on-disk
>>structures. It should say "oh not one of mine, skipping". Instead it
>>returns an error claiming massive corruption, and halts the system. I
>>just upgraded my wifes computer from Suse to RedHat FC4 and when it hits
>>the reiser partitions, the whole system explodes due to fsck.ext3
>>misrecognizing reiser partitions.
>>
>>
>
>Since when does fsck run fsck.ext3 on filesystems that are not marked
>as ext3 in /etc/fstab?
>
>
>
>>I had to modify rc.sysinit and blank
>>the partitions with fdisk to get it to install. After it installed, I
>>recreated the partitions (after writing down what they were in the first
>>place for block #'s etc.) and disabled rc.sysinit checks. This is
>>busted. Hans needs to fix fsck.ext3 and submit a patch or redhat does.
>>
>>
>
>Sorry, but I doubt that Hans or anybody in RH knows how to patch
>
---> wetware, <----
Is this the new "official" non-official slang word for Suse Linux?
Jeff
>let alone one as messed up as yours.
>-
>
>
next prev parent reply other threads:[~2005-10-09 23:40 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 [this message]
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
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=4349961F.7060109@utah-nac.org \
--to=jmerkey@utah-nac.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox