Re: Honest timeline for btrfsck

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

 



On Sun, Oct 9, 2011 at 4:13 AM, Asdo <asdo@xxxxxxxxxxxxx> wrote:
> On 10/07/11 22:19, Diego Calleja wrote:
>>
>> On Viernes, 7 de Octubre de 2011 21:10:33 Asdo escribió:
>>>
>>> failures, but you can always mount by rolling back to a previous
>>> uberblock, showing an earlier view of the filesystem, which would be
>>> consistent.
>>
>> This is already available in Btrfs, command btrfsck -s.
>
> Whops!? Then I am wondering what causes these corrupted unmountable
> filesystems.

"-s" does not select previous uberblock. It selects alternate uberblock.

> I think that in Btrfs wiki (which is now down) there was written that btrfs
> was substantially stable, with the only exception that a power loss combined
> with drives not honoring barriers could result in an unmountable
> filesystems.

for this condition btrfs-zero-log will be more useful

-- 
Fajar
--
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


[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