On Tue, May 15, 2012 5:13 pm, Ben Myers wrote:
> On Tue, May 15, 2012 at 02:58:42AM +0200, Patrick Shirkey wrote:
>> Unfortunately I cannot unmount the partition/s to run xfs_metadump
>> they are in use.
>> I have found some files that were truncated on a recent crash. Is there
>> any tool I can run on those files to get info that might be useful?
> Hrm.. xfs_bmap output could be helpful so we can see the block map. Do
> know how big they are supposed to be? How much was truncated?
The files that we have as examples were originally 28bytes but are now 0byte.
Running xfs_bmap on the 0 byte file returns "no extent".
These files are located next to each other in the same folder.
- 28 byte file:
EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET
0: [0..7]: 28230136440..28230136447 13 (312849120..312849127)
- 0 byte file: no extents
> Unfortunately since you don't know which database will have the
> you'll need to get xfs_bmap output for all of them, and then after a crash
> the 'after'. Is that a possibility?
I'll try to get some more data.
- Separately I was able to run xfs_metadump against one of our partitions.
The resulting file is 1.4 GB and it also has some potentially sensitive
information in it so I am not sure about posting it to a public location.
Is there anything that I can look for that might be useful.
I have some data from xfs_bmap on specific files located in the same
partition as the metadump was generated from. I'm not sure if that will
actually give us any details that can help though as this data is all post
- A few more details that may be relevant.
1: We are running openvz and LVM on these machines. Are there any known
issue/s with file corruption after a hard reset with openvz/LVM running?
2: We have observed that while there is no obvious pattern in the data
corruption is does happen in chunks. It appears to be random chunks of
files that are corrupted after a crash->reset sequence.
Boost Hardware Ltd