[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52B2A807.5000608@disconnect.de>
Date: Thu, 19 Dec 2013 09:02:15 +0100
From: arno <arno@...connect.de>
To: Dave Chinner <david@...morbit.com>
CC: xfs@....sgi.com, linux-kernel@...r.kernel.org
Subject: Re: [XFS BUG] xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Structure
needs cleaning
On 18-Dec-13 11:33 PM, Dave Chinner wrote:
> On Wed, Dec 18, 2013 at 04:00:42PM +0100, arno wrote:
>> Hello,
>>
>> (Please keep me in CC, I'm not subscribed)
>>
>> Just got "xfs_growfs: XFS_IOC_FSGROWFSDATA xfsctl failed: Structure
>> needs cleaning" when trying to grow a logical Volume. Sorry, I lost the
>> xfs_growfs output.
>>
>> After collecting some info, I ran xfs_repair, and that seemed to fix it,
>> so no harm done. After fixing, the FS had the new, increased size, if
>> that matters.
>
> This isn't the first time you've grown the filesystem, is it?
No, indeed it isn't.
> On older kernels, growfs could leave trailing garbage in the new
> secondary superblocks it created. This was fixed in kernel v3.8 by
> commit:
>
> 1375cb6 xfs: growfs: don't read garbage for new secondary superblocks
>
> This garbage is detected by other changes made in v3.8 that verify
> the secondary superblocks as they are read.
>
> 9802182 xfs: verify superblocks as they are read from disk
>
> So if you grew the filesystem on a kernel older than v3.8, growing
> it again on a v3.8+ kernel will detect the superblock corruption and
> throw this error.
I'm pretty sure that last time I grew it, it was with a pre v3.8-kernel.
> xfs_repair was recently fixed to detect the garbage in secondary
> superblocks and zero it:
>
> cbd7508 xfs_repair: zero out unused parts of superblocks
>
> So what you need to do is run xfs_repair built from the development
> git tree and run it on your filesystem. That will remove the garbage
> from the superblocks and make this problem go away forever.
Will do. Thanks!
--
Regards.
Arno.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists