From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Rodrigo Barbosa (aka morcego)" <rodrigob@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, Stephen Tweedie <sct@redhat.com>
Subject: Re: Renaming lost+found
Date: Sat, 27 Jan 2001 20:43:24 +0000 [thread overview]
Message-ID: <20010127204324.B14943@redhat.com> (raw)
In-Reply-To: <20010126141350.Q6979@capsi.com> <Pine.LNX.3.95.1010126084632.208A-100000@chaos.analogic.com> <20010126131949.A1041@bessie.dyndns.org> <20010126180554.I19067@conectiva.com.br>
In-Reply-To: <20010126180554.I19067@conectiva.com.br>; from rodrigob@conectiva.com.br on Fri, Jan 26, 2001 at 06:05:54PM -0200
Hi,
On Fri, Jan 26, 2001 at 06:05:54PM -0200, Rodrigo Barbosa (aka morcego) wrote:
>
> I think JFS indeed doesn't have it. And ReiserFS doesn't too. This
> should be common place for journaling filesystems.
No, it's nothing to do with journaling or not. Even journaling
filesystems can suffer IO errors or corrupt disk blocks, and any case
where you have a file whose name has been lost due to such corruption
needs to be dealt with by the fsck tool. Traditionally, fsck puts
such files into lost+found, and in the presence of data corruption, it
will still need to do so even with a journaling filesystem.
ext3 uses lost+found in exactly the same way as ext2 for this reason.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-27 20:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-26 13:13 Renaming lost+found Rob Kaper
2001-01-26 13:49 ` Richard B. Johnson
2001-01-26 18:19 ` James Lewis Nance
2001-01-26 20:05 ` Rodrigo Barbosa (aka morcego)
2001-01-27 20:43 ` Stephen C. Tweedie [this message]
2001-01-28 19:26 ` Chris Mason
2001-01-27 23:14 ` Thunder from the hill
2001-01-28 21:35 ` H. Peter Anvin
2001-01-28 21:41 ` Mo McKinlay
2001-01-28 21:56 ` Support for 802.11 cards? Mike Pontillo
2001-01-28 22:07 ` John Jasen
2001-01-28 23:23 ` Michael H. Warfield
2001-01-29 0:13 ` Joe deBlaquiere
2001-01-29 2:00 ` Anton Blanchard
2001-01-29 18:18 ` Bryan O'Sullivan
2001-01-30 1:09 ` Mike Pontillo
2001-01-29 6:41 ` Renaming lost+found Mike Galbraith
2001-01-29 7:17 ` Andreas Dilger
2001-01-31 15:32 ` tytso
2001-01-26 19:24 ` Andreas Dilger
2001-01-26 19:45 ` patrick.mourlhon
[not found] ` <200101262005.PAA05246@mah21awu.cas.org>
2001-01-26 20:21 ` patrick.mourlhon
-- strict thread matches above, loose matches on Subject: below --
2001-01-26 22:09 NDias
2001-01-27 21:01 ` Albert D. Cahalan
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=20010127204324.B14943@redhat.com \
--to=sct@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigob@conectiva.com.br \
/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