This patch makes btrfsck ignore (for now) options passed to it. This makes btrfsck runs on startup not failing. I was asked to post my patch here by the Debian Maintainer of btrfs-tools. Background: On Startup all filesystem (on a Debian system) are fsck''ed. A option to allow non-interactive filesystem checks on startup is passed to fsck, usually -a or -y. Currently btrfsck expects the device as the only parameter and fails if run with any option e.g. btrfsck -a /dev/hda1 (returns error code 1). My patch fixes this by allowing options to be passed, although all options are ignored at the moment. (The attached patch is slightly improved from the one I sent to the Debian bug report [1] before.) Please comment if this is acceptable for inclusion in btrfsck. If not, I would be happy to improve the patch. Thanks, Sten [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681 -- 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
[This time with the patch attached.] [Please CC: me, as I am not subscribed to the linux-btrfs mailing list.] This patch makes btrfsck ignore (for now) options passed to it. This makes btrfsck runs on startup not failing. I was asked to post my patch here by the Debian Maintainer of btrfs-tools. Background: On Startup all filesystem (on a Debian system) are fsck''ed. A option to allow non-interactive filesystem checks on startup is passed to fsck, usually -a or -y. Currently btrfsck expects the device as the only parameter and fails if run with any option e.g. btrfsck -a /dev/hda1 (returns error code 1). My patch fixes this by allowing options to be passed, although all options are ignored at the moment. (The attached patch is slightly improved from the one I sent to the Debian bug report [1] before.) Please comment if this is acceptable for inclusion in btrfsck. If not, I would be happy to improve the patch. Thanks, Sten [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567681