On 8 September 2012 01:39, Theodore Ts'o <tytso@xxxxxxx> wrote: > On Fri, Sep 07, 2012 at 09:12:49PM +0100, Mike Fleetwood wrote: >> >> Is it safe to read the super block off disk using ext2fs_open() or by >> running dumpe2fs for a mounted file system? What if the file system has >> just been resized? Are there any other methods for querying the total >> file system size? > > Yes, it would be safe to read the superblock off a mounted disk. > There is always going to be a race if someone is resizing the file > system as you read the file system, but that's true for the statfs > system call as well. It would also be easiest if GParted can use the free blocks from the on disk super block too, rather than calling statvfs(). How up to date will the on disk free blocks figure be? My testing using a slowly allocating space workload finds ext2 writes the super block every 6 seconds keeping the blocks free figure up to date. However for ext3 & ext4 the super block doesn't change. I guess because all the meta data updates are journalled and can be replayed on crash. Freezing and unfreezing ext3/4 does get the blocks free figure in the super block updated, but GParted shouldn't be freezing and unfreezing a file system just to get the free space. I guess that GParted should just use statvfs() to query free blocks. Thanks, Mike -- 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
