Fwd: Interaction of nodatacow and snapshots

e nodatacow files. 5. results are unpredictable and unreliable. 6. the snapshot removes the nodatacow attribute from everything on the original subvolume. 7. everything works fine (this one requires lots of imagination). I would appreciate cc's on the reply. Thanks. Ross Boylan

csum errors on negative root id?

balReserve, single: total=512.00MiB, used=0.00B $ sudo btrfs inspect-internal subvolid-resolve -- -9 /mnt/storage ERROR: -9: negative value is invalid. $ sudo btrfs inspect-internal inode-resolve 1303 /mnt/storage ERROR: ino paths ioctl: No such file or directory Please keep me CCed, thanks! Ross

limits on number of snapshots

an Buster which is 4.19 at the moment (4.18 on my first install). Thanks. I'd appreciate if you'd cc me on replies. Ross Boylan

Lockdep splat with v4.18.6

sg and one passed through kasan_symbolize.py for files, line numbers, etc. Thanks, - Ross btrfs_splat Description: Binary data btrfs_splat_symbolized Description: Binary data

Re: [PATCH v4 00/73] XArray version 4

I missed this from a previous version, but can you explain the motivation for replacing the radix tree with an xarray? (I think this should probably still be part of the cover letter?) Do we have a performance problem we need to solve? A code complexity issue we need to solve? Something else? - R

Re: [PATCH v7 15/22] dax: set errors in mapping when writeback fails

ore > > fsync(2). So convert DAX to using standard error reporting through the > > mapping. > > > > Signed-off-by: Jeff Layton > > Reviewed-by: Jan Kara > > Reviewed-by: Christoph Hellwig > > Reviewed-and-Tested-by: Ross Zwisler > > --- > > fs/d

Re: [PATCH v3 06/20] dax: set errors in mapping when writeback fails

On Mon, Apr 24, 2017 at 09:22:45AM -0400, Jeff Layton wrote: > In order to get proper error codes from fsync, we must set an error in > the mapping range when writeback fails. > > Signed-off-by: Jeff Layton Works fine in some error injection testing. Tested-by: Ross Zwisler >

Re: [PATCH 37/45] drivers: use req op accessor

th the previous commit. This doesn't occur if you don't use DAX, but based on the content of the commit I'm guessing that difference is due to variations in the way the two paths use discard. - Ross -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code

08 00 00 RIP [] unlock_page+0xa5/0xb0 mm/filemap.c:833 RSP ---[ end trace d419bf59bba263fb ]--- I'm happy to provide any additional info you need, or to test fixes. Thanks, - Ross -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message t

Help with crash on mount issue

I filed a bug for null pointer dereferences I started hitting: https://bugzilla.kernel.org/show_bug.cgi?id=76451 Noticing qgroup in the trace, I tried disabling/re-enabling quota support for the filesystem. That turned out to be a mistake. Now as soon as I mount, I'm getting an oops thanks to btr

[PATCH] btrfs-progs: Make btrfs_header_chunk_tree_uuid() return unsigned long

Internally, btrfs_header_chunk_tree_uuid() calculates an unsigned long, but casts it to a pointer, while all callers cast it to unsigned long again. >From btrfs commit b308bc2f05a86e728bd035e21a4974acd05f4d1e Signed-off-by: Ross Kirk --- btrfs-find-root.c |3 +-- cmds-chunk.c |

[PATCH v2] btrfs-progs: Make btrfs_header_fsid() return unsigned long

Internally, btrfs_header_fsid() calculates an unsigned long, but casts it to a pointer, while all callers cast it to unsigned long again. Committed to btrfs as fba6aa75654394fccf2530041e9451414c28084f Fix line length issues and match changes to kernelspace Signed-off-by: Ross Kirk --- cmds

[PATCH] btrfs-progs: Make btrfs_header_fsid() return unsigned long

Internally, btrfs_header_fsid() calculates an unsigned long, but casts it to a pointer, while all callers cast it to unsigned long again. Committed to btrfs as fba6aa75654394fccf2530041e9451414c28084f Signed-off-by: Ross Kirk --- cmds-chunk.c |6 ++ ctree.c | 18

[PATCH v3] btrfs: remove unused parameter from btrfs_header_fsid

Remove unused parameter, 'eb'. Unused since introduction in 5f39d397dfbe140a14edecd4e73c34ce23c4f9ee Updated to be rebased against current upstream and correct diff supplied this time! Signed-off-by: Ross Kirk --- fs/btrfs/ctree.c | 10 +- fs/btrfs/ctree.h |2 +-

[PATCH v2] btrfs: remove unused parameter from btrfs_header_fsid

Remove unused parameter, 'eb'. Unused since introduction in 5f39d397dfbe140a14edecd4e73c34ce23c4f9ee Updated to be rebased against current upstream. Signed-off-by: Ross Kirk --- fs/btrfs/ctree.c | 10 +- fs/btrfs/ctree.h |2 +- fs/btrfs/disk-io.c |6 +++---

[PATCH] btrfs-progs: remove unused parameter from btrfs_header_fsid

Remove unused parameter, 'eb'. Unused since introduction in e63b425f1444d2472ea05a6b2b9cf865f35b Signed-off-by: Ross Kirk --- cmds-chunk.c |4 ++-- ctree.c | 12 ++-- ctree.h |2 +- disk-io.c|2 +- print-tree.c |2 +- utils.c |2 +

[PATCH] btrfs: remove unused parameter from btrfs_header_fsid

Remove unused parameter, 'eb'. Unused since introduction in 5f39d397dfbe140a14edecd4e73c34ce23c4f9ee Signed-off-by: Ross Kirk --- fs/btrfs/ctree.c | 10 +- fs/btrfs/ctree.h |2 +- fs/btrfs/disk-io.c |6 +++--- fs/btrfs/ioctl.c |2 +- 4 files changed, 10

[PATCH] btrfs-progs: drop unused parameter from btrfs_item_nr

Remove unused eb parameter from btrfs_item_nr, unused since introduced in e63b425f1444d2472ea05a6b2b9cf865f35b Signed-off-by: Ross Kirk --- btrfs-calc-size.c |2 +- btrfs-image.c |6 +++--- cmds-restore.c|2 +- ctree.c | 30

Re: [PATCH] btrfs: drop unused parameter from btrfs_item_nr

On 16 September 2013 16:50, David Sterba wrote: > On Mon, Sep 16, 2013 at 03:58:09PM +0100, Ross Kirk wrote: >> Remove unused eb parameter from btrfs_item_nr > > Hmm it's been unused since day one > > 5f39d397dfbe140a14edecd4e73c34ce23c4f9ee > Mon Oct 15 16:14:19

[PATCH] Drop unused parameter from btrfs_item_nr

Unused parameter cleanup Ross Kirk (1): btrfs: drop unused parameter from btrfs_item_nr fs/btrfs/backref.c|2 +- fs/btrfs/ctree.c | 34 +- fs/btrfs/ctree.h | 13 ++--- fs/btrfs/dir-item.c |2 +- fs/btrfs/inode-item.c |2

[PATCH] btrfs: drop unused parameter from btrfs_item_nr

Remove unused eb parameter from btrfs_item_nr Signed-off-by: Ross Kirk --- fs/btrfs/backref.c|2 +- fs/btrfs/ctree.c | 34 +- fs/btrfs/ctree.h | 13 ++--- fs/btrfs/dir-item.c |2 +- fs/btrfs/inode-item.c |2 +- fs/btrfs

Re: Is my btrfs filesystem definitely dead?

Sébastien Luttringer seblu.net> writes: > > Hello, after a crash with linux 3.8.0, I'm unable to mount my btrfs root > filesystem. I tried with a archlinux rescue cd with a linux 3.7.5, but I > got the following errors: > > First trying to fix the fs: > > # btrfsck > usage: btrfsck dev > Btr

Re: BTRFS Bug

lAAmNz0%3D On 12 November 2012 23:08, Liu Bo wrote: > On Mon, Nov 12, 2012 at 10:37:58PM +0800, Ross Moore wrote: >> Hi, >> >> I have a BTRFS filesystem that seems to be suffering from a few >> problems. I'll post the first one, which looks most bizarre to me. >&

BTRFS Bug

s: bdev /dev/sda errs: wr 44273, rd 2378244, flush 0, corrupt 429, gen 0 If I attempt to rebalance, the kernel crashes after a while, well before it has had a chance to complete. Any assistance greatly appreciated, and I hope I can also help identify a bug with help. Thanks, Ross -- To unsubscribe