From: Hans-Werner Hilse <hilse@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: disk full but lot of space
Date: Mon, 8 Aug 2005 16:50:02 +0200 [thread overview]
Message-ID: <20050808165002.56725adb.hilse@web.de> (raw)
In-Reply-To: <200508081553.54266.gentoo@depardo.ch>
Hi,
On Mon, 8 Aug 2005 15:53:54 +0200
gentoo@depardo.ch wrote:
> I've attached the output of e2fsck -n. Could you please tell me how bad it
> looks? Are there questions to which answering yes is dangerous?
>
> e2fsck 1.26 (3-Feb-2002)
> Warning! /dev/hda2 is mounted.
That is done in a mounted situation. I guess, it is even read/write-
mounted?
Well, I'll cite the man page:
---snip
Note that in general it is not safe to run e2fsck on mounted
filesystems. The only exception is if the -n option is specified, and -
c, -l, or -L options are not specified. However, even if it is safe
to do so, the results printed by e2fsck are not valid if the filesystem
is mounted.
---snip
This is very harsh, I'd say, remounting it ro (read-only), sync'ing it
and then doing "e2fsck -n" will give a lot more valid information.
In mounted state, esp. read-write, it is pretty normal on a busy system
to have these inconsistencies the e2fsck dump showed...
-hwh
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-08 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 10:59 [gentoo-user] OT: disk full but lot of space gentoo
2005-08-08 11:28 ` Christoph Gysin
2005-08-08 11:55 ` gentoo
2005-08-08 12:10 ` Christoph Gysin
2005-08-08 12:40 ` gentoo
2005-08-08 12:56 ` Christoph Gysin
2005-08-08 13:53 ` gentoo
2005-08-08 14:05 ` Christopher Fisk
2005-08-08 22:14 ` Raymond Lillard
2005-08-12 22:46 ` mat
2005-08-08 14:50 ` Hans-Werner Hilse [this message]
2005-08-08 19:10 ` Jonathan Nichols
2005-08-08 11:57 ` Norberto Bensa
2005-08-08 12:09 ` gentoo
2005-08-08 12:09 ` Christoph Gysin
2005-08-08 13:54 ` Christopher Fisk
2005-08-09 2:17 ` Norberto Bensa
2005-08-09 11:26 ` Christoph Gysin
2005-08-14 7:30 ` Norberto Bensa
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=20050808165002.56725adb.hilse@web.de \
--to=hilse@web.de \
--cc=gentoo-user@lists.gentoo.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