On 11/3/18 5:20 PM, Nikolay Borisov wrote:
On 3.11.18 г. 3:34 ч., Su Yue wrote:
On 2018/11/2 10:10 PM, Christoph Anton Mitterer wrote:
Hey Su.
Sorry for the late reply cause I'm busy at other things.
Anything further I need to do in this matter or can I consider it
"solved" and you
On 3.11.18 г. 3:34 ч., Su Yue wrote:
>
>
> On 2018/11/2 10:10 PM, Christoph Anton Mitterer wrote:
>> Hey Su.
>>
>
> Sorry for the late reply cause I'm busy at other things.
>
>> Anything further I need to do in this matter or can I consider it
>> "solved" and you won't need further testing
On Sat, 2018-11-03 at 09:34 +0800, Su Yue wrote:
> Sorry for the late reply cause I'm busy at other things.
No worries :-)
> I just looked through related codes and found the bug.
> The patches can fix it. So no need to do more tests.
> Thanks to your tests and patience. :)
Thanks for fixing :-)
On 2018/11/2 10:10 PM, Christoph Anton Mitterer wrote:
Hey Su.
Sorry for the late reply cause I'm busy at other things.
Anything further I need to do in this matter or can I consider it
"solved" and you won't need further testing by my side, but just PR the
patches of that branch? :-)
Hey Su.
Anything further I need to do in this matter or can I consider it
"solved" and you won't need further testing by my side, but just PR the
patches of that branch? :-)
Thanks,
Chris.
On Sat, 2018-10-27 at 14:15 +0200, Christoph Anton Mitterer wrote:
> Hey.
>
>
> Without the last patches
Hey.
Without the last patches on 4.17:
checking extents
checking free space cache
checking fs roots
ERROR: errors found in fs roots
Checking filesystem on /dev/mapper/system
UUID: 6050ca10-e778-4d08-80e7-6d27b9c89b3c
found 619543498752 bytes used, error(s) found
total csum bytes: 602382204
[Bad format in previous reply, send again]
On 10/18/18 10:41 PM, Christoph Anton Mitterer wrote:
Hey.
So I'm back from a longer vacation and had now the time to try out your
patches from below:
On Wed, 2018-09-05 at 15:04 +0800, Su Yue wrote:
I found the errors should blame to something
On 10/18/18 10:41 PM, Christoph Anton Mitterer wrote:
Hey.
So I'm back from a longer vacation and had now the time to try out your
patches from below:
On Wed, 2018-09-05 at 15:04 +0800, Su Yue wrote:
I found the errors should blame to something about inode_extref check
in lowmem mode.
I
Hey.
So I'm back from a longer vacation and had now the time to try out your
patches from below:
On Wed, 2018-09-05 at 15:04 +0800, Su Yue wrote:
> I found the errors should blame to something about inode_extref check
> in lowmem mode.
> I have writeen three patches to detect and report errors
On 2018/9/5 8:33 PM, Christoph Anton Mitterer wrote:
On Wed, 2018-09-05 at 15:04 +0800, Su Yue wrote:
Agreed with Qu, btrfs-check shall not try to do any write.
Well.. it could have been just some coincidence :-)
I found the errors should blame to something about inode_extref check
in
On Wed, 2018-09-05 at 15:04 +0800, Su Yue wrote:
> Agreed with Qu, btrfs-check shall not try to do any write.
Well.. it could have been just some coincidence :-)
> I found the errors should blame to something about inode_extref check
> in lowmem mode.
So you mean errors in btrfs-check... and
On 09/04/2018 04:24 AM, Christoph Anton Mitterer wrote:
Hey.
On Fri, 2018-08-31 at 10:33 +0800, Su Yue wrote:
Can you please fetch btrfs-progs from my repo and run lowmem check
in readonly?
Repo: https://github.com/Damenly/btrfs-progs/tree/lowmem_debug
It's based on v4.17.1 plus additonal
On Tue, 2018-09-04 at 17:14 +0800, Qu Wenruo wrote:
> However the backtrace can't tell which process caused such fsync
> call.
> (Maybe LVM user space code?)
Well it was just literally before btrfs-check exited... so I blindly
guesses... but arguably it could be just some coincidence.
LVM tools
On 2018/9/4 上午4:24, Christoph Anton Mitterer wrote:
> Hey.
>
>
> On Fri, 2018-08-31 at 10:33 +0800, Su Yue wrote:
>> Can you please fetch btrfs-progs from my repo and run lowmem check
>> in readonly?
>> Repo: https://github.com/Damenly/btrfs-progs/tree/lowmem_debug
>> It's based on v4.17.1
Hey.
On Fri, 2018-08-31 at 10:33 +0800, Su Yue wrote:
> Can you please fetch btrfs-progs from my repo and run lowmem check
> in readonly?
> Repo: https://github.com/Damenly/btrfs-progs/tree/lowmem_debug
> It's based on v4.17.1 plus additonal output for debug only.
I've adapted your patch to
Thank for the report.
On 08/31/2018 12:47 AM, Christoph Anton Mitterer wrote:
Hey.
I've the following on a btrfs that's basically the system fs for my
notebook:
When booting from a USB stick with:
# uname -a
Linux heisenberg 4.17.0-3-amd64 #1 SMP Debian 4.17.17-1
(2018-08-18) x86_64
Hey.
I've the following on a btrfs that's basically the system fs for my
notebook:
When booting from a USB stick with:
# uname -a
Linux heisenberg 4.17.0-3-amd64 #1 SMP Debian 4.17.17-1
(2018-08-18) x86_64 GNU/Linux
# btrfs --version
btrfs-progs v4.17
... a lowmem mode fsck gives no error:
#
17 matches
Mail list logo
