Re: [PATCH] generic/466: be more precise about which block sizes to use

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]



On Wed, Dec 13, 2017 at 09:36:29AM -0800, Darrick J. Wong wrote:
> > +	get_page_size
> > +	;;
> > +    *)
> > +	echo 512
> 
> FWIW XFS' minimum block size is 1k for v5 filesystems, though you can't
> really tell until you run mkfs.xfs -N.

Ok, but I assume we should keep this at 512 since it could be a v4
file systems that are being tested?

> > +_fs_max_blocksize()
> > +{
> > +    get_page_size
> 
> Also, one can run xfstests against a fuse2fs-mounted 64k-block ext4 fs.

Really?  Does mmap work on a fuse2fs-mounted 64k-block ext4 file system?

I suppose can just force the block size to be 64k for fuse2fs,
although I don't think the using some file system like ext4 for
fuse2fs testing isn't going to work right now anyway, yes?

	      	   	     		     	       - Ted
--
To unsubscribe from this list: send the line "unsubscribe fstests" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystems Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux