From: Eric Sandeen <sandeen@redhat.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Filessystem corruptions while using rsnapshot
Date: Wed, 09 Sep 2009 16:46:12 -0500 [thread overview]
Message-ID: <4AA82224.3010605@redhat.com> (raw)
In-Reply-To: <20090909214223.GB2011@phenom2.trippelsdorf.de>
Markus Trippelsdorf wrote:
> On Wed, Sep 09, 2009 at 04:35:45PM -0500, Eric Sandeen wrote:
...
>> Just for completeness, if there are errors in the system logs, can you
>> post them here as well?
>
> There are no errors in the system logs.
> I only learned about this bug when a regular boot-time fsck was running that
> printed the problems mentionted above.
Hm, but there should be no regular boot-time fsck unless you have your
forced-fsck interval set pretty low; a normal boot-time fsck will simply
replay the log. Was that it; did you just happen to catch this on the
21st boot or whatever the interval may be?
Otherwise, the fs was flagged with errors, and -that- forced the full
fsck at boot time, and hopefully something previous was logged somewhere ...
-Eric
next prev parent reply other threads:[~2009-09-09 21:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 13:30 Filessystem corruptions while using rsnapshot Markus Trippelsdorf
2009-09-09 14:40 ` Eric Sandeen
2009-09-09 14:54 ` Markus Trippelsdorf
2009-09-09 17:20 ` Markus Trippelsdorf
2009-09-09 17:21 ` Eric Sandeen
2009-09-09 21:29 ` Markus Trippelsdorf
2009-09-09 21:35 ` Eric Sandeen
2009-09-09 21:42 ` Markus Trippelsdorf
2009-09-09 21:46 ` Eric Sandeen [this message]
2009-09-09 21:50 ` Markus Trippelsdorf
[not found] ` <4AA82C62.40305@redhat.com>
2009-09-10 1:11 ` Markus Trippelsdorf
2009-09-17 20:33 ` Markus Trippelsdorf
2009-09-17 20:39 ` Eric Sandeen
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=4AA82224.3010605@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=markus@trippelsdorf.de \
/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;
as well as URLs for NNTP newsgroup(s).