From: Andreas Dilger <adilger@turbolabs.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
linux-kernel@vger.kernel.org
Subject: Re: ext3 vs resiserfs vs xfs
Date: Wed, 7 Nov 2001 13:21:25 -0700 [thread overview]
Message-ID: <20011107132125.I5922@lynx.no> (raw)
In-Reply-To: <Pine.LNX.4.30.0111071558090.29292-100000@mustard.heime.net> <E161UYR-0004S5-00@the-village.bc.nu> <5.1.0.14.2.20011107183639.0285a7e0@pop.cus.cam.ac.uk>
In-Reply-To: <5.1.0.14.2.20011107183639.0285a7e0@pop.cus.cam.ac.uk>; from aia21@cam.ac.uk on Wed, Nov 07, 2001 at 06:40:21PM +0000
On Nov 07, 2001 18:40 +0000, Anton Altaparmakov wrote:
> Hm, while still on the default RH7.2 kernel using ext3 on all partitions I
> flicked the reset switch accidentally (wrong reset switch it was...) and
> when coming back up it fscked (I didn't touch anything - didn't even notice
> any 5 second thing but I wasn't looking at this screen) and it found two
> lost inodes (I got two entries in lost and found). So it still needs to
> fsck by the looks of it?
Well, e2fsck will always run if the filesystem has an error marked in it.
When was the last time you ran e2fsck on the fs before you converted to
ext3? It is possible that these lost inodes were in the fs before you
converted?
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-07 20:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-07 15:00 Roy Sigurd Karlsbakk
2001-11-07 15:23 ` Alan Cox
2001-11-07 15:28 ` Zvi Har'El
2001-11-07 20:19 ` Andreas Dilger
2001-11-07 21:11 ` Zvi Har'El
2001-11-07 21:25 ` Christian Bornträger
2001-11-07 21:45 ` Mike Fedyk
2001-11-07 21:42 ` Andreas Dilger
2001-11-07 22:11 ` arjan
2001-11-07 21:48 ` arjan
2001-11-08 7:08 ` Zvi Har'El
2001-11-08 11:06 ` Arjan van de Ven
2001-11-08 12:10 ` Zvi Har'El
2001-11-08 12:11 ` Arjan van de Ven
2001-11-08 11:35 ` ramfs leak Padraig Brady
2001-11-07 16:31 ` ext3 vs resiserfs vs xfs James A Sutherland
2001-11-07 19:38 ` Ville Herva
2001-11-07 20:44 ` James A Sutherland
2001-11-07 21:11 ` Andreas Dilger
2001-11-07 21:37 ` ext3 vs resizerfs " Ville Herva
2001-11-07 21:45 ` Andreas Dilger
2001-11-08 0:13 ` ext3 vs resiserfs " James A Sutherland
2001-11-07 19:50 ` Daniel Gryniewicz
2001-11-07 20:24 ` Robert Love
2001-11-07 20:35 ` Andrew Morton
2001-11-07 20:27 ` Anton Altaparmakov
2001-11-07 18:40 ` Anton Altaparmakov
2001-11-07 19:12 ` Alan Cox
2001-11-07 20:36 ` Anton Altaparmakov
2001-11-07 19:40 ` Anton Altaparmakov
2001-11-07 20:15 ` Andrew Morton
2001-11-07 21:33 ` Mike Fedyk
2001-11-07 22:00 ` Andrew Morton
2001-11-07 22:27 ` Mike Fedyk
2001-11-07 22:56 ` Andrew Morton
2001-11-07 23:18 ` Andreas Dilger
2001-11-07 22:52 ` Mike Fedyk
2001-11-07 22:59 ` Andrew Morton
2001-11-07 23:36 ` D. Stimits
2001-11-07 23:55 ` Mike Castle
2001-11-07 23:38 ` Mike Castle
2001-11-07 23:49 ` Mike Fedyk
2001-11-08 10:58 ` Juan Quintela
2001-11-07 20:25 ` Andreas Dilger
2001-11-07 23:33 ` Ryan Cumming
2001-11-09 16:11 ` Andreas Dilger
2001-11-07 20:21 ` Andreas Dilger [this message]
2001-11-07 20:05 ` Theodore Tso
2001-11-07 20:18 ` Andreas Dilger
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=20011107132125.I5922@lynx.no \
--to=adilger@turbolabs.com \
--cc=aia21@cam.ac.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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®