mkfs.xfs should align the file system according to the exported device topology info.
Good summary page:
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
The plan is to export this info via libblkid as a standard interface, so this bug probably needs to depend on that feature (in util-linux-ng).
hch has sent patches to the xfs list for this.
The patch is now upstream.
Eric, do you want to backport it for more test coverage? I hope we can spin a new xfsprogs release end of November / early December with the topology support and the repair memory usage improvements.
Thanks Christoph; I think we've likely missed the boat for F12 (we'd need updated blkid too, probably too much to sneak in now, though I can ask) and for RHEL5 the kernel bits are totally missing, so we'll probably just have to get it pushed into RHEL6 as soon as possible - after util-linux-ng gets an update ....
(we should ping sgi to pull to their tree too I suppose)
1799792 build (dist-f13, /cvs/pkgs:rpms/xfsprogs/devel:xfsprogs-3_0_3-2_fc13) completed successfully
Built in rawhide, now.
$ rpm -qp --changelog xfsprogs-3.0.3-3.el6.x86_64.rpm | more
* Fri Nov 20 2009 Eric Sandeen <email@example.com> 3.0.3-3
- Fix up build issues w.r.t. off64_t
* Tue Nov 10 2009 Eric Sandeen <firstname.lastname@example.org> 3.0.3-2
- Add trim/discard & libblkid support
the libblkid patch makes use of the topology info (which libdisk did before, anyway).
Actually I only got this right in xfsprogs-3.0.3-5 :)
What's in RHEL6 -today- is still missing these bits, but it should get pulled to RHEL6.
Ok, RHEL6 bits should be good now.
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.