So you think this might be a bug in the Kernel? In fact I wanted to
try with a newer kernel, but could no longer reproduce the issue.
In addition, I did a scrub on the partition and there were no errors.
So wither there was some transient disk issue that affected only that
partition, or there is a
On Mon, Apr 17, 2017 at 02:00:45PM -0400, Alexandru Guzu wrote:
> Not sure if anyone is looking into that segfault, but I have an update.
> I disconnected the USB drive for a while and today I reconnected it
> and it auto-mounted with no issue.
>
> What is interesting is that the drive letter chan
Not sure if anyone is looking into that segfault, but I have an update.
I disconnected the USB drive for a while and today I reconnected it
and it auto-mounted with no issue.
What is interesting is that the drive letter changed to what is was
before when it was working.
Remember that in my first e
Thanks for the reply.
I mounted it ro:
$ sudo btrfs fi show /mnt
Segmentation fault (core dumped)
dmesg says:
...
kernel BUG at /build/linux-wXdoVv/linux-4.4.0/fs/btrfs/ctree.c:5205!
...
RIP: 0010:[] []
btrfs_search_forward+0x268/0x350 [btrfs]
...
Call Trace:
[] search_ioctl+0xf2/0x1
Can you ro mount it and:
btrfs fi show /mnt
btrfs fi df /mnt
And then next update the btrfs-progs to something newer like 4.9.2 or
4.10.2 and then do another 'btrfs check' without repair. And then
separately do it again with --mode=lowmem and post both sets of
results?
Chris Murphy
--
To unsubs
Hello,
I am not sure how to better summarize this but I'll give a more
detailed description.
I am using btrfs tools v4.4, I setup up a btrfs partition on an
external USB2 drive and I started to play with it.
The partition was about HALF full when I decided to run duperemove on
it. This took a whi
