| To: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, Gabriel VLASIU <gabriel@xxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair and xfs filesystem strange behaviour |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Mon, 22 Jun 2015 07:38:10 -0500 |
| Cc: | xfs-oss <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20150622133338.6b78ed75@xxxxxxxxxxxxxxxxxxxx> |
| References: | <alpine.LRH.2.11.1506201447380.21027@xxxxxxxxxxxxxxx> <20150622133338.6b78ed75@xxxxxxxxxxxxxxxxxxxx> |
On 6/22/15 6:33 AM, Emmanuel Florac wrote: > Le Sat, 20 Jun 2015 15:16:26 +0300 (EEST) > Gabriel VLASIU <gabriel@xxxxxxxxxx> Ãcrivait: > >> Every time I erase the files in lost+found directory and then run >> xfs_repair I got the same errors and the same files are saved back to >> lost+found. If I do not remove anything from lost+found directory no >> errors are reported by xfs_repair. >> >> xfsprogs 3.2.1 >> kernel 4.0.5 x86_64 >> >> How can I get rid of the 0 bytes files in lost+found directory? > > First of all try the latest xfs_repair, version 3.2.3 . It's common > for a new version to be able to tame previously uncorrectable > corruptions. Worth trying, yes. I've also connected w/ Gabriel to obtain a metadump to look at, if that doesn't work. Thanks, -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_repair and xfs filesystem strange behaviour, Emmanuel Florac |
|---|---|
| Next by Date: | Re: xfs_repair and xfs filesystem strange behaviour, Brian Foster |
| Previous by Thread: | Re: xfs_repair and xfs filesystem strange behaviour, Emmanuel Florac |
| Next by Thread: | Re: xfs_repair and xfs filesystem strange behaviour, Gabriel VLASIU |
| Indexes: | [Date] [Thread] [Top] [All Lists] |