From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.15aa1
Date: Mon, 26 Nov 2001 11:14:54 -0500 [thread overview]
Message-ID: <200111261614.fAQGEsP01603@deathstar.prodigy.com> (raw)
In-Reply-To: <1006629351.1470.8.camel@praetorian>
In-Reply-To: <20011124085028.C1419@athlon.random>
In article <1006629351.1470.8.camel@praetorian> aafes@psu.edu asked:
| -=-=-=-=-=-
|
| On Sat, 2001-11-24 at 02:50, Andrea Arcangeli wrote:
| > Only in 2.4.15aa1: 00_iput-unmount-corruption-fix-1
| >
| > Fix iput umount corruption.
|
| Is this the problem that Al put out a patch for yesterday? And is his
| patch been tested and working?
|
| > Only in 2.4.15aa1: 00_read_super-stale-inode-1
| >
| > If read_super fails avoid lefting stale inodes queued into
| > the superblock.
|
| What is this? How dangerous is it?
Good question. As I read the patch, the problem occurs during umount,
when dirty inodes are not (properly) written to the disk. Would a sync()
help or eliminate this problem, assuming that all files were closed?
Hopefully someone knows, I don't want to tell you it only happens at
umount, but that's my impression.
In any case, since 2.4.16 is out (so much for "2.4.15 released without
embarrassment") to fix the problem, I would go with that unless you have
a reason to use whichever patch pleases you.
--
bill davidsen <davidsen@tmr.com>
His first management concern is not solving the problem, but covering
his ass. If he lived in the middle ages he'd wear his codpiece backward.
prev parent reply other threads:[~2001-11-26 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 7:50 2.4.15aa1 Andrea Arcangeli
2001-11-24 9:45 ` 2.4.15aa1 Paulo J. Matos aka PDestroy
2001-11-24 10:05 ` 2.4.15aa1 Andrea Arcangeli
2001-11-24 19:15 ` 2.4.15aa1 Phil Sorber
2001-11-24 19:34 ` 2.4.15aa1 Russell King
2001-11-24 19:39 ` 2.4.15aa1 Andrea Arcangeli
2001-11-26 16:14 ` bill davidsen [this message]
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=200111261614.fAQGEsP01603@deathstar.prodigy.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®