From: Jonathan Sergent <sergent@IO.COM>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] making better use of ext2fs?
Date: Mon, 14 May 2001 10:17:39 -0700 [thread overview]
Message-ID: <20010514171739.DC62B199F2@mail.cse.psu.edu> (raw)
>apart from not sync'ing on shutdown
Even there, it's not been to bad to me--rolling blackouts, ^P. I did
end up with some strange corruption once when this happened, but wrap
made it easy to figure out which system files got busted, and it
hasn't happened since then.
OTOH I suffered through many instances of having to suffer through
e2fsck and losing data when Linux ran on the same machine. (And I
couldn't use the packaging database to check for what was busted,
because it turned into a subdirectory after the fsck was done.)
Am I confused or is the problem with data corruption on unclean
shutdown with kfs the same as with ext2, namely that there aren't
synchronous metadata updates?
next reply other threads:[~2001-05-14 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-14 17:17 Jonathan Sergent [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 18:10 forsyth
2001-05-14 12:25 forsyth
2001-05-14 10:36 Aharon Robbins
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=20010514171739.DC62B199F2@mail.cse.psu.edu \
--to=sergent@io.com \
--cc=9fans@cse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).