Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4
From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Date: Mon, 9 Mar 2015 10:44:06 -0600
In-reply-to: <1425905102.1178.27.camel@gmx.de>

Maybe try btrfs-progs-3.19rc3? You have the data backed up, and progs
3.18.2 fails so it seems worth a shot.


Chris Murphy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4
  - From: Tobias Getzner

References:
- Lock-ups, assertion failure in btrfsck, scrub reporting super=4
  - From: Tobias Getzner
- Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4
  - From: Duncan
- Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4
  - From: Tobias Getzner

Prev by Date: Re: [PATCH 1/2] Btrfs: send, add missing check for dead clone root
Next by Date: Re: [PATCH 2/2] Btrfs: send, don't leave without decrementing clone root's send_progress
Previous by thread: Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4
Next by thread: Re: Lock-ups, assertion failure in btrfsck, scrub reporting super=4
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux