On Tue, Sep 09, 2008 at 09:43:47AM -0400, Theodore Tso wrote: > The alternate is to create an entire new program (e4migrate) just to > trigger a single ioctl. The reality is this is probably going to more > used by ext4 developers than anybody else, since it's rare that you > would want to convert a single file from using indrect blocks to using > extents. In general, most users/system administrators will want to > convert the entire filesystem; eventually this will probably be done > via some combination with the userspace program to trigger online > defrag, but this was just a stopgap measure to allow us to more easily > exercise the kernel code more than anything else. > > So given that this is only to enable extents on a single file, "chattr > +e file" is very much in line with the rest of the chattr interface > for setting other flags. Well, if you think setting a flag is a good interface to convert to extents, then do it all the way and allow setting the extent flag in the kernel through FS_IOC_SETFLAGS instead of having an interface schism. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
