From: Eric Sandeen <sandeen@redhat.com>
To: Kevin Shanahan <kmshanah@ucwb.org.au>
Cc: linux-ext4@vger.kernel.org
Subject: Re: More ext4 corruption
Date: Fri, 03 Apr 2009 18:25:12 -0500 [thread overview]
Message-ID: <49D69AD8.6070808@redhat.com> (raw)
In-Reply-To: <20090403221508.GA5436@kulgan>
Kevin Shanahan wrote:
> Hi,
>
> I'm seeing some more corruption on our ext4 filesystems. Last night's
> backup job had these errors:
>
...
> rsync: readlink "/srv/samba/local/apps/CIM8/Release-Notes/rc_200410_01.htm" failed: Input/output error (5)
> rsync: readlink "/srv/samba/local/apps/CIM8/Release-Notes/rc_200709_01.pdf" failed: Input/output error (5)
> IO error encountered -- skipping file deletion
> skipping non-regular file "apps/CIM8/Release-Notes/rb_200803_02.pdf"
> rsync error: some files could not be transferred (code 23) at main.c(1524) [generator=3.0.3]
> setfacl: apps/CIM8/Release-Notes/rb_200803_02.pdf: No such file or directory
>
> The "apps/Gestalt.Net/..." error is an old one and I need to chase
> that up some more[1]. The corruption in the "Release-Notes" directory
> is new last night.
>
> My initial information gathering is below. Let me know what else might
> be helpful, but I'll have to fsck before Monday.
Any kernel messages this time? You could also run e2fsck -n and provide
that output (it should not actually modify anything)
Thanks,
-eric
> [1] http://marc.info/?l=linux-ext4&m=123695451828101&w=2
>
> Regards,
> Kevin.
next prev parent reply other threads:[~2009-04-03 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 22:15 More ext4 corruption Kevin Shanahan
2009-04-03 23:25 ` Eric Sandeen [this message]
2009-04-04 10:52 ` Kevin Shanahan
2009-04-04 16:23 ` Theodore Tso
2009-04-04 21:39 ` Kevin Shanahan
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=49D69AD8.6070808@redhat.com \
--to=sandeen@redhat.com \
--cc=kmshanah@ucwb.org.au \
--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;
as well as URLs for NNTP newsgroup(s).