Re: [PATCH 1/6] xstat: Add a pair of system calls to make extended file stats available
- From: Dave Chinner <david fromorbit com>
- To: David Howells <dhowells redhat com>
- Cc: Andreas Dilger <adilger dilger ca>, linux-cifs vger kernel org, linux-nfs vger kernel org, nautilus-list gnome org, libc-alpha sourceware org, kfm-devel kde org, wine-devel winehq org, samba-technical lists samba org, linux-api vger kernel org, linux-fsdevel vger kernel org, linux-ext4 vger kernel org
- Subject: Re: [PATCH 1/6] xstat: Add a pair of system calls to make extended file stats available
- Date: Fri, 27 Apr 2012 10:51:21 +1000
On Thu, Apr 26, 2012 at 02:32:36PM +0100, David Howells wrote:
> Andreas Dilger <adilger dilger ca> wrote:
> > st_blksize may be variable for a distributed filesystem,
It can be variable for local filesystems, too. XFS will vary the
block size based on the configuration of the inode. e.g. if there is
an extent allocation size hint on the inode, or it's on the realtime
device, and so on. There is no guarantee that from file to file that
it is constant.
> I wonder if there's a way to make this explicit - or is it something that if
> the bit isn't set, you can't use the value in st_blksize.
> I wonder if this
> value always has to be non-zero to make sure existing stat() doesn't explode.
More likely it probably needs to be non-zero to prevent applications
doing division by block size from exploding... ;)
Cheers,
Dave.
--
Dave Chinner
david fromorbit com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]