unsubscribe linux-kernel
--
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
On 04/14/2018 03:45 PM, Timo Nentwig wrote:
On 04/14/2018 11:42 AM, Qu Wenruo wrote:
And the work load when the RO happens is also helpful.
(Well, the dmesg of RO happens would be the best though)
I had a glance at dmesg but don't remember anything specific (think
the usual " [cut
On 04/14/2018 11:42 AM, Qu Wenruo wrote:
And the work load when the RO happens is also helpful.
(Well, the dmesg of RO happens would be the best though)
Surprisingly nothing special AFAIR. It's a private, mostly idle machine.
Probably "just" browsing with chrome.
I didn't notice the remount
Hi!
btrfs remounted itself ro during operation (don't have the dmesg) and
fails to mount after reboot.
Any advice?
4.15.15-1-ARCH #1 SMP PREEMPT Sat Mar 31 23:59:25 UTC 2018 x86_64 GNU/Linux
btrfs-progs v4.16
Label: '830' uuid: 22e778f7-2499-4379-99d2-cdd399d1cc6e
Total devices 1
Hi there,
I had remote filesystem not unmounting during shutdown so I hit the reboot
button. Did so a couple of times in the past. 3.6.8-1-ARCH, btrfs-progs
0.19.20121005-4, don't remember the exact version I used when creating the
filesystem (0.19 something).
btrfsck looks like this:
On Wed, 15 Feb 2012, Chris Mason wrote:
Date: Wed, 15 Feb 2012 08:23:22 -0500
From: Chris Mason chris.ma...@oracle.com
To: Timo Nentwig bt...@nentwig.biz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: can't read superblock (but could mount)
On Wed, Feb 15, 2012 at 07:03:49AM +0100, Timo
On Mon, 13 Feb 2012, Chris Mason wrote:
btrfs-debug-tree -b 9872289792 /dev/xxx
# btrfs-debug-tree -b 9872289792 /dev/loop1
leaf 9872289792 items 51 free space 0 generation 120351 owner 5
fs uuid 9e9886fc-3e60-4c59-a246-727662769ee2
chunk uuid f7e4ac1e-f4d6-436b-9bda-8409311dcdb6
item
On Tue, 14 Feb 2012, Chris Mason wrote:
As for how we got here, I think you said you were originally running
something older than 3.2 when these problems started, correct?
Nope, I was already on 3.2.1 or 3.2.4. I restored a backup in the meantime
and already had to soft-reset the box:
# ls
On Tue, 14 Feb 2012, Chris Mason wrote:
Ok, 3.2 shouldn't have done this. Was this an external drive? What
else do you have on the system?
Nothing special actually. Standard arch linux with virtualbox kernel modules.
It's a SSD if this should matter. Mounted with ssd,compress=lzo,noatime.
