| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: file corruption |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Thu, 1 Apr 2004 20:48:27 -0800 |
| In-reply-to: | <20040402043920.GF21226@xxxxxxxxxxxxxxx> |
| References: | <406AF7B6.6030405@xxxxxxxxxxxxxxx> <20040402001801.GA24900@xxxxxxxxxxxxxxxxxxxxxxx> <406CB95B.4040500@xxxxxxxxxxxxxxx> <20040402043920.GF21226@xxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Thu, Apr 01, 2004 at 07:39:20PM -0900, Ethan Benson wrote: > I have seen this a few times as well, except the binary crap is > usually PREpended rather then appended to the file, also the end of > the file is usually cut off, as if the start and end markers were > equally offset backwards. (the start of the file moved back 5 or 10 > bytes, and the end of the file moved back 5 or 10 bytes, thus causing > truncation and random crud being prepended). How much data are we talking about here? For > blocksize this seems impssible. --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: file corruption, Chris Wedgwood |
|---|---|
| Next by Date: | TAKE 909055 - make 2.4/2.6 pb ioerror same, Nathan Scott |
| Previous by Thread: | Re: file corruption, Ethan Benson |
| Next by Thread: | Re: file corruption, Ethan Benson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |