On 03.04.2017 12:11, Robert Krig wrote:
> Hi guys, I seem to have run into a spot of trouble with my btrfs partition.
>
> I've got 4 x 8TB in a RAID1 BTRFS configuration.
>
> I'm running Debian Jessie 64 Bit, 4.9.0-0.bpo.2-amd64 kernel. Btrfs
> progs version v4.7.3
>
> Server has 8GB of Ram.
>
>
> I was running duperemove using a hashfile, which seemed to have run out
> space and aborted. Then I tried a balance operation, with -dusage
> progressively set to 0 1 5 15 30 50, which then aborted, I presume that
> this caused the fs to mount readonly. I only noticed it somewhat later.
>
> I've since rebooted, and I can mount the filesystem OK, but after some
> time (I presume caused by reads or writes) it once again switches to
> readonly.
>
> I tried unmounting/remounting again and running a scrub, but the scrub
> aborts after some time.
>
>
I've compiled the newest btrfs-tools version 4.10.2
This is what I get when running a btrfsck -p /dev/sda
hecking filesystem on
/dev/sda
UUID:
8c4f8e26-3442-463f-ad8a-668dfef02593
incorrect offsets 8590
1258314415
bad block
38666170826752
ERROR: errors found in extent allocation tree or chunk
allocation
Speicherzugriffsfehler
For the non-german speakers: Speicherzugriffsfehler = Memory Access Error
Dmesg shows this:
Apr 03 15:47:05 atlas kernel: btrfs[9140]: segfault at 9476b99e ip
000000000044c459 sp 00007fff556b4b10 error 4 in
btrfs[400000+9d000]
--
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
