From: "Jeff Merkey" <jmerkey@timpanogas.org>
To: "Alexander Viro" <viro@math.psu.edu>,
"Robert Boermans" <boermans@tfn.net>
Cc: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.0 breakage even with fix?
Date: Sat, 24 Nov 2001 16:14:03 -0700 [thread overview]
Message-ID: <007901c1753d$b541ae80$f5976dcf@nwfs> (raw)
In-Reply-To: <Pine.GSO.4.21.0111241749320.6117-100000@weyl.math.psu.edu>
Al,
I am not seeing any more breakage with this fix with NWFS.
Jeff
----- Original Message -----
From: "Alexander Viro" <viro@math.psu.edu>
To: "Robert Boermans" <boermans@tfn.net>
Cc: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>; <linux-kernel@vger.kernel.org>
Sent: Saturday, November 24, 2001 4:03 PM
Subject: Re: 2.5.0 breakage even with fix?
>
>
> On Sun, 25 Nov 2001, Robert Boermans wrote:
>
> > If the filesystem is marked clean, does that mean that people with
> > journalling file systems are fscked? (since there might be no journal
entry
> > of what hasn't finished.)
>
> Well, if filesystem doesn't have a recovery tool that would allow forced
> check mode - you _are_ screwed. As you will be again and again if you get
> memory corruption/driver bugs/fs bugs/RAID bugs/physical disk
problems/etc.
>
> Again, if filesystem trusts clear bit to the extent that you have no way
> to convince it that checks _are_ needed - it's unfit for any serious use.
> I suspect that by now everybody had learnt that much - that used to be
> a permanent source of problems with early journalling filesystems and
AFAIK
> all of them had been fixed since then.
>
> -
> 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/
next prev parent reply other threads:[~2001-11-24 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 0:54 2.5.0 breakage even with fix? Petr Vandrovec
2001-11-24 0:13 ` Alexander Viro
2001-11-24 23:05 ` Robert Boermans
2001-11-24 23:03 ` Alexander Viro
2001-11-24 23:14 ` Jeff Merkey [this message]
2001-11-24 0:23 ` Andreas Dilger
-- strict thread matches above, loose matches on Subject: below --
2001-11-24 1:05 Petr Vandrovec
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='007901c1753d$b541ae80$f5976dcf@nwfs' \
--to=jmerkey@timpanogas.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=boermans@tfn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.