On Sun, Aug 19, 2018 at 04:31:55PM -0400, Ryan Kavanagh wrote: > On Mon, Jul 31, 2017 at 05:50:44PM +0200, Adam Borowski wrote: > > > btrfs-progs (4.12-1) unstable; urgency=medium > > > [ Nicholas D Steeves ] > > > * Drop btrfs-convert (Closes: #824895, #854489) > > > > Yes, there are some caveats, but the man page discusses them at length. > > If you decide to continue to exclude btrfs-convert from btrfs-progs, > please also drop the manpage: > > rak@zeta:~$ dpkg -S btrfs-convert > btrfs-progs: /usr/share/man/man8/btrfs-convert.8.gz > > It took me a bit of searching to figure out why there was a manpage but > no associated binary.
Ryan, You're 100% right. Duncan, on linux-btrfs, also suggested the possibility of shipping a dummy script, and it would be easier to maintain one of those (eg: like fsck.btrfs) than to rebase a patch with every release. Please ping me if references to btrfs-convert aren't patched out by mid-October. Dmitri, I'm guessing you'll prefer the dummy script? Re: upstream btrfs-convert status, there was recently a thread on linux-btrfs@vger on this topic. The portion of the wiki page that said it hasn't been tested much since linux-4.0 was pulled, but the official status was not clarified. I specifically asked if SUSE support btrfs-convert for its paying customers, and a few other question...no reply. Currently btrfs-convert will mysteriously fail if ever it cannot allocate a large enough empty extent of contiguous free space. IIRC upstream patches were submitted to output better error messages if this occurs. Cheers, Nicholas
signature.asc
Description: PGP signature
