On 2016-07-05 15:55, Tomasz Chmielewski wrote:
On 2016-07-05 14:56, Tomasz Chmielewski wrote:
Getting this lengthy output logged, and the fs mounter read-only after
a power outage.
Tried also 4.6.3, but it ends just alike.
Jul 5 02:04:20 bkp011 kernel: [ 799.298303] [ cut here
]
On Sat, Jul 9, 2016 at 11:30 AM, Tomáš Hrdina wrote:
> sudo btrfs rescue super-recover -v /dev/sda
> All Devices:
> Device: id = 1, name = /dev/sdc
> Device: id = 2, name = /dev/sdb
> Device: id = 3, name = /dev/sda
>
> Before Recovering:
> [All good supers]:
>
sudo btrfs rescue super-recover -v /dev/sda
All Devices:
Device: id = 1, name = /dev/sdc
Device: id = 2, name = /dev/sdb
Device: id = 3, name = /dev/sda
Before Recovering:
[All good supers]:
device name = /dev/sdc
superblock bytenr =
On Fri, Jul 8, 2016 at 11:30 PM, Andrei Borzenkov wrote:
> 09.07.2016 00:50, Chris Murphy пишет:
>>>
>>> Instead those utilities should employ rootflags=subvol or subvolid to
>>> explicitly use a particular fs tree for rootfs, rather that hide this
>>> fact by using subvolume set-default.
>>
>> Th
