Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum

xfs

Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum

To:	Eric Sandeen <sandeen@xxxxxxxxxx>
Subject:	Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum
From:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:	Tue, 20 Sep 2011 16:30:40 -0400
Cc:	xfs-oss <xfs@xxxxxxxxxxx>, Boris Ranto <branto@xxxxxxxxxx>
In-reply-to:	<4E77B7E2.6020805@xxxxxxxxxx>
References:	<4E77B7E2.6020805@xxxxxxxxxx>
User-agent:	Mutt/1.5.21 (2010-09-15)

On Mon, Sep 19, 2011 at 04:45:06PM -0500, Eric Sandeen wrote:
> RH QA discovered this bug:
> 
> Steps to Reproduce:
> 1. Create 4 TB - 1 B partition
> dd if=/dev/zero of=x.img bs=1 count=0 seek=4398046511103
> 2. Create xfs fs with 512 B block size on the partition
> mkfs.xfs -b size=512 xfs.img

Can we please get this into xfstests, just doing the mkfs on a
sparse file should be enough.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[PATCH] mkfs.xfs: don't increase agblocks past maximum, Eric Sandeen Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum, Alex Elder Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum, Eric Sandeen Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum, Alex Elder Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum, Christoph Hellwig <=

Previous by Date:	Re: xfs_repair segfaut in stage 6, Christoph Hellwig
Next by Date:	[PATCH 1/4] libxfs: handle read errors in libxfs_trans_read_buf, Christoph Hellwig
Previous by Thread:	Re: [PATCH] mkfs.xfs: don't increase agblocks past maximum, Alex Elder
Next by Thread:	Re: xfs_repair: add printf format checking and fix the fallout, Alex Elder
Indexes:	[Date] [Thread] [Top] [All Lists]