From: Eric Sandeen <sandeen@sandeen.net>
To: adamantzj <tzj1983@163.com>
Cc: xfs@oss.sgi.com
Subject: Re: power failure causes files loss
Date: Fri, 23 Apr 2010 15:40:47 -0500 [thread overview]
Message-ID: <4BD205CF.80203@sandeen.net> (raw)
In-Reply-To: <28340118.post@talk.nabble.com>
adamantzj wrote:
> Hello,
>
> I’m writing data on a server in my company, but power cut suddenly. I
> had to restart the machine, then I found that many files in the working
> directory had been lost. I made some tries with xfs_repair and it didn't
> repair my corrupted file.
>
> What are the reasons caused this problem? I would like to know is what can I
> do to resolve this problem? Is XFS able to recover my file with its right
> content, at least a consistent content?
Well, anything written via buffered IO but not synced could be lost, in general.
This is true for any filesystem.
Also, depending on your storage, if barriers were not enabled on something with
a volatile write cache, this can cause problems on a power loss. This would be
the case on lvm on rhel5 for example (if you had write caches on your drives).
You didn't say if repair found any problems, or if the filesystem had trouble
mounting post-loss, etc... this would be useful info.
But in general, unsynced buffered data -will- be lost on a power loss, for any
fs.
-Eric
> I'm running a 2.6.24 kernel with xfsprogs-3.1.1, and the operating
> system is RedHat Enterprise Linux 5 Server (64-bit).
>
> Do you know if this problem has often been encountered, there is a way
> to proceed?
>
> Thank you !
>
> Adamant
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-23 20:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 11:28 power failure causes files loss adamantzj
2010-04-23 20:40 ` Eric Sandeen [this message]
2010-04-23 22:25 ` Stan Hoeppner
2010-04-24 17:05 ` Hans-Peter Jansen
2010-04-24 19:21 ` Eric Sandeen
2010-04-24 21:12 ` Emmanuel Florac
2010-04-25 9:43 ` Peter Grandi
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=4BD205CF.80203@sandeen.net \
--to=sandeen@sandeen.net \
--cc=tzj1983@163.com \
--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