From: Steven Smith <sos22@cam.ac.uk>
To: linux-newbie@vger.kernel.org
Subject: Re: File-system Ext2 or Ext3??
Date: Sun, 12 May 2002 17:54:21 +0100 [thread overview]
Message-ID: <20020512165421.GA1066@cam.ac.uk> (raw)
In-Reply-To: <20020512152519.38384.qmail@web12808.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
> > > still get forced fscks at startup,
> > How many? ext3 should be fscked every 20 or so times
> > it gets mounted,
> > to find any errors which crept in from somewhere.
> 20 boots at about average a week per boot, I shouldn't
> be seeing a fsck for 5 months. :(
> Instead I'm getting them more like every third bootup.
Does fsck say why it's running? There will usually be messages saying
(from memory) ``not cleanly unmounted'' or ``has been mounted ... times''
just before fsck proper starts.
> > ``Linux native'' isn't terribly well defined,
> YES! I'd noticed that before...how unhelpful is THAT,
> of course it's Linux Native, duh it's /, it HAS to be
> Linux Native to be mounted at startup!
It might be UMSDOS...
> > fdisk assumes ext2 is the One
> > True Linux Filesystem, so gives the wrong answer if
> > something else is used.
> > It should probably just say Linux.
> Yes...in a nutshell that sounds like I thought it
> might be, oversimplication of fs.
> There's so many apps that need to be upgraded and
> rewritten....
True, but it's far easier to just ignore the filesystem type field.
It's only supposed to be a hint, anyway.
Steven Smith,
sos22@cam.ac.uk.
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2002-05-12 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 20:46 File-system Ext2 or Ext3?? Staci
2002-05-12 12:44 ` Edgar Alwers
2002-05-12 15:09 ` Steven Smith
2002-05-12 15:10 ` Dan Milne
2002-05-12 15:25 ` Staci
2002-05-12 16:54 ` Steven Smith [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=20020512165421.GA1066@cam.ac.uk \
--to=sos22@cam.ac.uk \
--cc=linux-newbie@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 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.