Ok then, many thanks.
In a letter from Friday, July 14, 2017 15:41:22 MSK user Qu Wenruo wrote:
>
> On 2017年07月14日 20:26, Filippe LeMarchand wrote:
> > So, my options are
> > a) Delete and re-create sobvolume
> > b) Try btrfs check --repair --mode original (if original
7月14日 20:04, Filippe LeMarchand wrote:
> >> Currently possible solution may be deleting the whole subvolume.
> > Can btrfs send (to external drive) and then btrfs receive back fix it? Or
> > should I use simple cp/rsync?
>
> You could try if you have backup.
>
>
ently and it didn't find any errors.
In a letter from Friday, July 14, 2017 14:28:58 MSK user Qu Wenruo wrote:
>
> On 2017年07月14日 18:12, Filippe LeMarchand wrote:
> > First "rm" on deprecated.txt worked, but file is still there. Neither the
> > file,
gt; filename ("depercated.txt", I assume the sxt one is caused by a memory
> bit corruption).
>
> So, any details on the operation with util-linux/deprecated.txt will
> help us to locate the root cause in kernel.
>
> Thanks,
> Qu
>
>
> On 2017年07月12日 2
19:12, Filippe LeMarchand wrote:
> >> Maybe something wrong in grep happened which skip "(79177" ?
> > Yes, my bad. Now I used grep -E "\(79177| 79177" pattern, file on GDrive
> > updated.
>
> It looks much better, thanks.
>
> >
> >
e=lowmem" to see if lowmem
> mode reports similar (well, output may differ) error?
>
> If lowmem mode also reports error on such DIR_ITEM, I'm pretty sure
> that's the problem.
>
> However it may take some time before we can fix it in repair mode.
>
> Thanks
Sure, here it is:
https://drive.google.com/drive/folders/0B1ax9Am81gx9YjJBVVA0LXRHeGc
In a letter dated Tuesday, July 4, 2017 16:16:36 MSK user Lu Fengqi wrote:
> On Mon, Jul 03, 2017 at 08:34:52AM +0800, Qu Wenruo wrote:
> >
> >
> >At 07/01/2017 07:59 PM, Filippe LeMarch
Hello everyone.
I have an btrfs root partition on Intel 530 ssd, which mounts without errors
and seem to work fine,
but `btrfs check` gives me foloowing output (and --repair doesn't remove
errors):
enabling repair mode
Checking filesystem on /dev/sda2
UUID: 12c84aa3-ce65-4390-807e-a72cc8a7445e