From: Raimund Andersen <anderse@gmx.de>
To: linux-ext4@vger.kernel.org
Subject: Re: Filesystem still has errors
Date: Wed, 11 Feb 2009 22:34:45 +0000 (UTC) [thread overview]
Message-ID: <loom.20090211T222920-494@post.gmane.org> (raw)
In-Reply-To: 49934EC8.7040800@redhat.com
Eric Sandeen <sandeen <at> redhat.com> writes:
>
> You should expect that checking a live filesystem will produce errors,
> actually. So don't worry about that. The filesystem is not quiesced,
> and it's not consistent. That is to be expected, and it's why you see
> the different behavior w/ forcefsck vs. e2fsck -n on the live fs.
>
> As for the spurious ENOSPC, I'm not certain. Do you still get the error?
Thanks for your quick reply. No, at the moment, I don't get it. Yesterday, it
occured once and a reboot let it vanish, and I got it some days before. Also
then, a reboot let it disappear. So could it be of help if I collect any
information in the case it might reappear? What exactly should I do then?
Thank you, once again.
rgds Raimund
next prev parent reply other threads:[~2009-02-11 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 22:13 Filesystem still has errors Raimund andersen
2009-02-11 22:18 ` Eric Sandeen
2009-02-11 22:34 ` Raimund Andersen [this message]
2009-02-11 22:36 ` Eric Sandeen
2009-02-11 22:40 ` Raimund Andersen
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=loom.20090211T222920-494@post.gmane.org \
--to=anderse@gmx.de \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox