All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: CPU: 6 PID: 13386 at fs/btrfs/ctree.h:1593 btrfs_update_device.cold+0x10/0x1b [btrfs]
Date: Tue, 5 Nov 2019 09:06:45 +0800	[thread overview]
Message-ID: <95982a1f-68dd-092a-3a47-3b8a6ffe67b3@gmx.com> (raw)
In-Reply-To: <1e6ad65de01b6808bf9acf781e55dd47@wpkg.org>


[-- Attachment #1.1: Type: text/plain, Size: 3154 bytes --]



On 2019/11/5 上午9:03, Tomasz Chmielewski wrote:
> On 2019-11-05 09:52, Qu Wenruo wrote:
> 
>>> Now let's try to unmount and see what "btrfs rescue fix-device-size"
>>> shows again - I'd expect "No device size related problem found",
>>> correct?
>>>
>>>
>>> # umount /home
>>>
>>> # btrfs rescue fix-device-size /dev/sda4
>>> parent transid verify failed on 265344253952 wanted 42646 found 46119
>>> parent transid verify failed on 265344253952 wanted 42646 found 46119
>>> parent transid verify failed on 265344253952 wanted 42646 found 46119
>>
>> This is not correct. What happened during your /home mount and unmount?
>>
>> The fs looks already screwed up.
> 
> Nothing happened - it normally mounts/unmounts without errors.
> 
> Also scrub works without issues (a few days ago):
> 
> # btrfs scrub status /home
> UUID:             c94ea4a9-6d10-4e78-9b4a-ffe664386af2
> Scrub started:    Sat Nov  2 01:14:17 2019
> Status:           finished
> Duration:         0:55:23
> Total to scrub:   1.17TiB
> Rate:             368.41MiB/s
> Error summary:    no errors found
> 
> 
> It also no longer shows "parent transid verify failed" after a few more
> cycles like this:
> 
> # umount /home
> 
> # btrfs rescue fix-device-size /dev/sda4
> parent transid verify failed on 265344253952 wanted 42646 found 46119
> parent transid verify failed on 265344253952 wanted 42646 found 46119
> parent transid verify failed on 265344253952 wanted 42646 found 46119
> Ignoring transid failure
> Fixed super total bytes, old size: 7901711842304 new size: 7901711835136
> Fixed unaligned/mismatched total_bytes for super block and device items

When this transid mismatch happens, it's highly recommended to do a
btrfs check on it.

I won't be surprised by some error.

> 
> # btrfs rescue fix-device-size /dev/sda4
> No device size related problem found
> 
> # mount /home ; sync ; umount /home
> 
> # btrfs rescue fix-device-size /dev/sda4
> parent transid verify failed on 265344253952 wanted 42646 found 46119
> parent transid verify failed on 265344253952 wanted 42646 found 46119
> parent transid verify failed on 265344253952 wanted 42646 found 46119
> Ignoring transid failure
> Fixed super total bytes, old size: 7901711842304 new size: 7901711835136
> Fixed unaligned/mismatched total_bytes for super block and device items
> 
> # mount /home ; sync ; umount /home
> 
> # btrfs rescue fix-device-size /dev/sda4
> No device size related problem found
> 
> # btrfs rescue fix-device-size /dev/sda4
> No device size related problem found
> 
> # mount /home ; sync ; umount /home
> 
> # btrfs rescue fix-device-size /dev/sda4
> No device size related problem found
> 
> # btrfs rescue fix-device-size /dev/sdb4
> No device size related problem found
> 
> # mount /home
> 
> # date > /home/date.txt
> 
> # umount /home
> 
> # btrfs rescue fix-device-size /dev/sdb4
> No device size related problem found

And that kernel warning still exists?

Thanks,
Qu
> 
> 
> 
> Tomasz Chmielewski
> https://lxadm.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2019-11-05  1:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02  1:13 CPU: 6 PID: 13386 at fs/btrfs/ctree.h:1593 btrfs_update_device.cold+0x10/0x1b [btrfs] Tomasz Chmielewski
2019-11-02  3:38 ` Qu Wenruo
2019-11-05  0:47   ` Tomasz Chmielewski
2019-11-05  0:52     ` Qu Wenruo
2019-11-05  1:03       ` Tomasz Chmielewski
2019-11-05  1:06         ` Qu Wenruo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=95982a1f-68dd-092a-3a47-3b8a6ffe67b3@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mangoo@wpkg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.