On Tue, Jan 15, 2013 at 12:44:36PM -0800, hopper@xxxxxxxxxxxxxxx wrote:
> Help! BTW, I'm not a mailing list subscriber.
Here is a sample fix that I believe will allow the offending filesystem
to at least be mounted. It hasn't been tested at all.
----------------------------
diff -ur kernel-3.7.fc17.orig/linux-3.7.2-201.fc17.x86_64/fs/btrfs/qgroup.c kernel-3.7.fc17/linux-3.7.2-201.fc17.x86_64/fs/btrfs/qgroup.c
--- kernel-3.7.fc17.orig/linux-3.7.2-201.fc17.x86_64/fs/btrfs/qgroup.c 2012-12-10 19:30:57.000000000 -0800
+++ kernel-3.7.fc17/linux-3.7.2-201.fc17.x86_64/fs/btrfs/qgroup.c 2013-01-15 14:02:39.643630137 -0800
@@ -379,8 +379,13 @@
ret = add_relation_rb(fs_info, found_key.objectid,
found_key.offset);
- if (ret)
+ /* Failing to add a relation because one side or the other
+ * doesn't exist isn't a fatal error here. */
+ if (ret) {
+ if (ret == -ENOENT)
+ ret = ENOENT;
goto out;
+ }
next2:
ret = btrfs_next_item(quota_root, path);
if (ret < 0)
----------------------------
--
"They who can give up essential liberty to obtain a little temporary
safety, deserve neither liberty nor safety." -- Benjanmin Franklin
-- Eric Hopper (http://www.omnifarious.org/~hopper) --
Attachment:
pgpx9etDlB91J.pgp
Description: PGP signature
