On Fri, Jun 06, 2008 at 12:53:39PM -0400, Martin K. Petersen wrote: > >>>>> "Dave" == Dave Chinner <david@xxxxxxxxxxxxx> writes: > > Dave> So is there going to be any obvious kernel API to access all > Dave> this info? i.e. if you do an online modification of a volume > Dave> (e.g. add new storage of a different geometry to the volume) > Dave> and then do an online grow of the filesystem, how does the > Dave> filesystem get that new geometry information for the expanded > Dave> area? > > xfs_growfs would call libdisk to see whether the topology had changed > since the fs was created. Sure it could, but xfs_growfs is currently just a wrapper around an ioctl that tells the kernel to grow the filesystem by N bytes and the kernel does all the changes transactionally. So changing xfs_growfs to provide this information to the kernel will require a new userspace API for XFS to push this information straight back down into the kernel.... Also, it would be good to verify that stored filesystem parameters are still optimal at mount time by querying the block device(s) when internal structures are first initialised from disk. Hence even a simple kernel API to this info would be handy. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
