From: Eric Sandeen <sandeen@sandeen.net>
To: Josh Endries <endries@cs.cornell.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Crash recovery/zero-byte file question
Date: Fri, 17 May 2013 16:44:07 -0500 [thread overview]
Message-ID: <5196A4A7.6010805@sandeen.net> (raw)
In-Reply-To: <731755347.10846.1368808589019.JavaMail.root@coecis.cornell.edu>
On 5/17/13 11:36 AM, Josh Endries wrote:
> Hello,
Hi Josh -
> We have a RHEL 6.3 machine with a large XFS mount that suffered a
> power outage.
For starters, have you engaged your RH support folks?
> When it came back up, it allegedly fixed itself, but
> now many files are zero bytes. I found a bug report/errata fix at RH
> that mentions something similar, which might be what we ran into.
Which one? RH support can probably help you decide if that bug report
applies, and where/when it was fixed.
> We
> are running a kernel that should have the fix as far as I can tell,
> but we definitely have zero byte files that shouldn't be.
shouldn't be because they had all been properly synced to disk
before the power loss, or? (just in general, files not fsynced
aren't guaranteed to be in any particular state if you lose power,
though of course there are certain expectations of timely flushing).
> My question is: is there a way to restore this or fix it before going
> to backups? Is it worth it to unmount and run xfs_check or similar?
> Unfortunately, since the system came up and appeared to be working,
> some users have been using that mount point.
If you have backups that's probably the best option.
-Eric
p.s. xfs_check is deprecated in favor of xfs_repair [-n]
> Thanks, Josh
>
> _______________________________________________ xfs mailing list
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-17 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1601451892.10839.1368808313900.JavaMail.root@coecis.cornell.edu>
2013-05-17 16:36 ` Crash recovery/zero-byte file question Josh Endries
2013-05-17 21:44 ` Eric Sandeen [this message]
2013-05-20 2:01 ` Josh Endries
2013-05-20 2:22 ` 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=5196A4A7.6010805@sandeen.net \
--to=sandeen@sandeen.net \
--cc=endries@cs.cornell.edu \
--cc=xfs@oss.sgi.com \
/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