| To: | Shailendra Tripathi <stripathi@xxxxxxxxx> |
|---|---|
| Subject: | Re: LVM and XFS cannot set blocksize on block device |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 27 Sep 2006 10:48:37 -0500 |
| Cc: | Chris Wedgwood <cw@xxxxxxxx>, Rene Salmon <rsalmon@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <451A669D.9020503@xxxxxxxxx> |
| References: | <45185424.2030707@xxxxxxxxxx> <20060926001737.GA10224@xxxxxxxxxxxxxxxxxxxxx> <45193204.3030500@xxxxxxxxxx> <20060926224053.GA31542@xxxxxxxxxxxxxxxxxxxxx> <451A669D.9020503@xxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5.0.7 (X11/20060913) |
Shailendra Tripathi wrote: > libxfs_device_open () seems to be working with the pre-conceived notion > of assuming block devices of only 512 bytes in size. > > if (!readonly && setblksize && (statb.st_mode & S_IFMT) == S_IFBLK) > platform_set_blocksize(fd, path, statb.st_rdev, 512); > > This eventually calls to set the blk sz to 512. Since, your volume does > not support less than 4k, it returns EINVAL. I think, libxfs_init should > be modified to take pass on the -s size option to this call so that it > does not happen. > However, I don't see any problem despite this failure. Everything > else should work fine. > Yep, this looks to me like an oversight when the larger-sector-size support was added. Seems like if the device can't be set to a smaller sector size than X, then the tools should run as if a sector size of X had been specified? -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: LVM and XFS cannot set blocksize on block device, Rene Salmon |
|---|---|
| Next by Date: | Re: [PATCH] xfs_db ring command, Timothy Shimmin |
| Previous by Thread: | Re: LVM and XFS cannot set blocksize on block device, Tim Shimmin |
| Next by Thread: | Re: LVM and XFS cannot set blocksize on block device, Tim Shimmin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |