linux-btrfs.vger.kernel.org archive mirror
 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 08:52:32 +0800	[thread overview]
Message-ID: <c44c5868-6351-4d38-de12-c7903b64a441@gmx.com> (raw)
In-Reply-To: <94c49648ea714dcd1f087f24ee796115@wpkg.org>


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



On 2019/11/5 上午8:47, Tomasz Chmielewski wrote:
> On 2019-11-02 12:38, Qu Wenruo wrote:
>> On 2019/11/2 上午9:13, Tomasz Chmielewski wrote:
>>> I'm getting these recently from time to time (first noticed in 5.3.x,
>>> but maybe they were showing up before and I didn't notice).
>>>
>>> Everything seems to work fine so far. Anything to worry about?
>>
>> This is a warning about unaligned device size.
>>
>> You can either fix it by reducing the device size by 4K for each device,
>> or use btrfs rescue fix-dev-size unmounted to repair.
> 
> Unfortunately "btrfs rescue fix-device-size" doesn't seem to help. I'm
> still seeing these entries in dmesg some time after using the command.
> 
> Also:
> 
> # umount /home
> 
> # btrfs rescue fix-device-size /dev/sdb4
> Fixed device size for devid 2, old size: 3950855921152 new size:
> 3950855917568
> Fixed device size for devid 3, old size: 3950855921152 new size:
> 3950855917568
> Fixed super total bytes, old size: 7901711842304 new size: 7901711835136
> Fixed unaligned/mismatched total_bytes for super block and device items

So far so good.

> 
> # btrfs rescue fix-device-size /dev/sdb4
> No device size related problem found
> 
> # btrfs rescue fix-device-size /dev/sda4
> No device size related problem found
> 
> # dmesg -c
> 
> # mount /home
> 
> 
> 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.

Thanks,
Qu

> Ignoring transid failure
> Fixed super total bytes, old size: 7901711842304 new size: 7901711835136
> Fixed unaligned/mismatched total_bytes for super block and device items
> 
> # 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 ; umount /home
> 
> # btrfs rescue fix-device-size /dev/sdb4
> 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
> 
> 
> 
> Tomasz Chmielewski
> https://lxadm.com


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

  reply	other threads:[~2019-11-05  0:52 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 [this message]
2019-11-05  1:03       ` Tomasz Chmielewski
2019-11-05  1:06         ` Qu Wenruo

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=c44c5868-6351-4d38-de12-c7903b64a441@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).