Am Sonntag, 18. November 2018, 01:30:14 CET schrieb Qu Wenruo:
> >>> Late on I got the same errors for my /home partition (on the same drive)
> >>> as well. I have snapshots of all partitions on another drive made by
> >>> btrbk. To get a working system, I made new (rw) snapshots of the most
> >>>
On 2018/11/18 上午4:28, Stephan Olbrich wrote:
> Am Samstag, 17. November 2018, 09:03:04 CET schrieb Qu Wenruo:
>> On 2018/11/17 上午12:17, Stephan Olbrich wrote:
>>> Hi,
>>>
>>> a few days ago my root file system (simple btrfs on a SSD, no RAID or
>>> anything) suddenly became read only. Looking at
Am Freitag, 16. November 2018, 17:44:35 CET schrieb Nikolay Borisov:
> On 16.11.18 г. 18:17 ч., Stephan Olbrich wrote:
> > Hi,
> >
> > a few days ago my root file system (simple btrfs on a SSD, no RAID or
> > anything) suddenly became read only. Looking at dmsg, I found this:
> >
> > [
Am Samstag, 17. November 2018, 09:03:04 CET schrieb Qu Wenruo:
> On 2018/11/17 上午12:17, Stephan Olbrich wrote:
> > Hi,
> >
> > a few days ago my root file system (simple btrfs on a SSD, no RAID or
> > anything) suddenly became read only. Looking at dmsg, I found this:
> >
> > [ 19.285020]
On 2018/11/17 下午5:49, Serhat Sevki Dincer wrote:
> Hi,
>
> On my second attempt to convert my 698 GiB usb HDD from ext4 to btrfs
> with btrfs-progs 4.19 from Manjaro (kernel 4.14.80):
>
> I identified bad files with
> $ find . -type f -exec cat {} > /dev/null \;
> This revealed 6 corrupted
Hi,
On my second attempt to convert my 698 GiB usb HDD from ext4 to btrfs
with btrfs-progs 4.19 from Manjaro (kernel 4.14.80):
I identified bad files with
$ find . -type f -exec cat {} > /dev/null \;
This revealed 6 corrupted files, I deleted them. Tried it again with
no error message.
Then I
On 2018/11/17 上午12:17, Stephan Olbrich wrote:
> Hi,
>
> a few days ago my root file system (simple btrfs on a SSD, no RAID or
> anything) suddenly became read only.
> Looking at dmsg, I found this:
>
> [ 19.285020] BTRFS error (device sda2): bad tree block start, want
> 705757184 have
