Message ID | 20110810155214.GE20461@twin.jikos.cz (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
On Wed, Aug 10, 2011 at 05:52:14PM +0200, David Sterba wrote: > there's a hardcoded path for mkfs.btrfs in common.rc:_scratch_mkfs_sized() > > 335 btrfs) > 336 /sbin/mkfs.$FSTYP $MKFS_OPTIONS $SCRATCH_DEV -b $fssize > 337 ;; > > I have a /usr/local/ installation of btrfsprogs from git, > _scratch_mkfs_sized() was not called for btrfs before. > > Possible ways to fix this: > 1) use /sbin/mkfs -t $FSTYP like _scratch_mkfs, or > 2) set $MKFS_BTRFS_PROG like for some other filesystems > > > What is preferred? Please send a patch for variant 2. As soon as we have option using the generic mkfs wrapper sounds like a good idea. In addition to that treating btrfs the same way as other filesystems is always good. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2011-08-10 at 17:52 +0200, David Sterba wrote: > Hi, > > On Mon, Aug 01, 2011 at 12:31:19PM +0200, Stefan Behrens wrote: > > Use _scratch_mkfs / _scratch_mkfs_sized instead of _scratch_mkfs_xfs > > where possible. > > Execute 015, 062, 083, 117, 120 and 192 for all filesystems, these > > tests used to be XFS specific. > > this patch is now in xfstests-dev and somehow breaks btrfs testing. . . . > there's a hardcoded path for mkfs.btrfs in common.rc:_scratch_mkfs_sized() > > 335 btrfs) > 336 /sbin/mkfs.$FSTYP $MKFS_OPTIONS $SCRATCH_DEV -b $fssize > 337 ;; > > I have a /usr/local/ installation of btrfsprogs from git, > _scratch_mkfs_sized() was not called for btrfs before. > > Possible ways to fix this: > 1) use /sbin/mkfs -t $FSTYP like _scratch_mkfs, or > 2) set $MKFS_BTRFS_PROG like for some other filesystems > > > What is preferred? Whatever works. My personal preference would be option (1) if it works, since it's does the generic thing directly rather than suggesting something special is needed for btrfs. But if that doesn't work, consistency rules so MKFS_BTRFS_PROG "like for some other filesystems" is good. -Alex -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, 2011-08-10 at 12:33 -0400, Christoph Hellwig wrote: > On Wed, Aug 10, 2011 at 05:52:14PM +0200, David Sterba wrote: > > there's a hardcoded path for mkfs.btrfs in common.rc:_scratch_mkfs_sized() > > > > 335 btrfs) > > 336 /sbin/mkfs.$FSTYP $MKFS_OPTIONS $SCRATCH_DEV -b $fssize > > 337 ;; > > > > I have a /usr/local/ installation of btrfsprogs from git, > > _scratch_mkfs_sized() was not called for btrfs before. > > > > Possible ways to fix this: > > 1) use /sbin/mkfs -t $FSTYP like _scratch_mkfs, or > > 2) set $MKFS_BTRFS_PROG like for some other filesystems > > > > > > What is preferred? > > Please send a patch for variant 2. As soon as we have option using > the generic mkfs wrapper sounds like a good idea. In addition to that > treating btrfs the same way as other filesystems is always good. Whoops, we gave different answers. Do what Christoph says... -Alex -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Aug 10, 2011 at 11:36:09AM -0500, Alex Elder wrote: > > Possible ways to fix this: > > 1) use /sbin/mkfs -t $FSTYP like _scratch_mkfs, or > > 2) set $MKFS_BTRFS_PROG like for some other filesystems > > > > > > What is preferred? > > Whatever works. My personal preference would be option (1) > if it works, since it's does the generic thing directly > rather than suggesting something special is needed for > btrfs. But if that doesn't work, consistency rules so > MKFS_BTRFS_PROG "like for some other filesystems" is good. Normally I'd agree with you, but I've run into problems with the generic mkfs binary, as it parses some options that might otherwise be left to the filesystem. E.g. it parses -l by itself, which causes problems when creating an xfs filesystem with an external log. Note that any filesystem supported by _scratch_mkfs_sized is special; there is no generic way to specify the size of a filesystem. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
--- 015.out 2011-02-11 11:42:29.000000000 +0100 +++ 015.out.bad 2011-08-10 17:19:48.000000000 +0200 @@ -1,7 +1,4 @@ QA output created by 015 -fill disk: - !!! disk full (expected) -check free space: -delete fill: -check free space: - !!! free space is in range +mkfs failed +(see 015.full for details) +umount: /mnt/sda10: not mounted $ check 062 --- 062.out 2011-08-10 17:17:23.000000000 +0200 +++ 062.out.bad 2011-08-10 17:20:57.000000000 +0200 @@ -49,10 +49,13 @@ user.name2=0xcafe *** remove attribute -SCRATCH_MNT/reg: user.name2: No such attribute +# file: SCRATCH_MNT/reg +user.name2 + <...long error output...> $ check 083 083 [failed, exit status 1] - output mismatch (see 083.out.bad) --- 083.out 2011-02-11 11:42:30.000000000 +0100 +++ 083.out.bad 2011-08-10 17:21:37.000000000 +0200 @@ -1,4 +1,5 @@ QA output created by 083