All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
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, 05 Nov 2019 09:47:48 +0900	[thread overview]
Message-ID: <94c49648ea714dcd1f087f24ee796115@wpkg.org> (raw)
In-Reply-To: <d24256c7-4398-7627-4352-1878af1467e9@gmx.com>

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

# 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
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

  reply	other threads:[~2019-11-05  0:47 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 [this message]
2019-11-05  0:52     ` Qu Wenruo
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=94c49648ea714dcd1f087f24ee796115@wpkg.org \
    --to=mangoo@wpkg.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    /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.