| To: | Eric Sandeen <sandeen@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH 5/5] xfs_repair: set proper ftype when moving to lost+found |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Sun, 07 Sep 2014 16:26:09 -0500 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1410108065-18156-6-git-send-email-sandeen@xxxxxxxxxx> |
| References: | <1410108065-18156-1-git-send-email-sandeen@xxxxxxxxxx> <1410108065-18156-6-git-send-email-sandeen@xxxxxxxxxx> |
On 9/7/14 11:41 AM, Eric Sandeen wrote: When we move files to lost+found, we're setting the filetype to UNKNOWN. This leaves an inconsistency which is discovered on a subsequent repair: would fix ftype mismatch (0/1) in directory/child inode 5838/5839 Setting the proper ftype at the time of the move resolves this: Ah, arekm points out that Jan already sent a patch to do this: [PATCH] repair: Set ftype for entries in lost+found http://oss.sgi.com/archives/xfs/2014-07/msg00314.html Sorry, missed that. -Eric |
| Previous by Date: | [PATCH 6/5] xfs_repair: don't re-add root dotdot if root dir was rebuilt, Eric Sandeen |
|---|---|
| Next by Date: | Re: storage, libaio, or XFS problem? 3.4.26, Dave Chinner |
| Previous by Thread: | [PATCH 5/5] xfs_repair: set proper ftype when moving to lost+found, Eric Sandeen |
| Next by Thread: | [PATCH 3/5] xfs_repair: fix dir refcount when '.' missing and dir is rebuilt, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |