From: Dave Chinner <david@fromorbit.com>
To: brian <a001@yakkadesign.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Repair Metadata corruption detected at xfs_inode_buf_verify on CentOS 7 virtual machine
Date: Fri, 10 Sep 2021 07:09:51 +1000 [thread overview]
Message-ID: <20210909210951.GD2361455@dread.disaster.area> (raw)
In-Reply-To: <8a959313-b7ab-5434-7c8f-1cf8990ecb4d@yakkadesign.com>
On Thu, Sep 09, 2021 at 03:11:45PM -0400, brian wrote:
> I switched over to ubuntu and got the error "Device or resource busy". How
> do I get around this error?
>
> Here is what I did:
> ---------------------------------------------------------
> sudo apt-get install qemu
> sudo apt install qemu-utils
> sudo apt-get install xfsprogs
>
> sudo modprobe nbd max_part=8
>
> sudo qemu-nbd --connect=/dev/nbd0
> /media/sf_virtual_machine_share/centoOS7Python3p9_tmp-disk1.vdi
>
> sudo xfs_repair /dev/nbd0p2
> ---------------------------------------------------------
>
> I got the error:
> ---------------------------------------------------------
> xfs_repair: cannot open /dev/nbd0p2: Device or resource busy
> ---------------------------------------------------------
Because /dev/nbd0p2 is not the device the filesystem is on. The
filesystem is on a lvm volume:
> brian@brian-VirtualBox:~/Desktop$ sudo lvmdiskscan
> /dev/loop0 [ 219.00 MiB]
> /dev/loop1 [ <55.44 MiB]
> /dev/sda1 [ 512.00 MiB]
> /dev/nbd0p1 [ 1.00 GiB]
> /dev/loop2 [ <65.10 MiB]
> /dev/nbd0p2 [ <101.71 GiB] LVM physical volume
As noted here.
> cmd:
> ---------------------------------------------------------
> sudo lvscan
> ---------------------------------------------------------
>
> Result:
> ---------------------------------------------------------
> ACTIVE '/dev/centos/swap' [2.00 GiB] inherit
> ACTIVE '/dev/centos/home' [<49.70 GiB] inherit
> ACTIVE '/dev/centos/root' [50.00 GiB] inherit
> ---------------------------------------------------------
And these are the devices inside the LVM volume that contain
filesystems/data.
Likely the one you are having trouble with is /dev/centos/root,
but there may be issues with /dev/centos/home, too.
And to answer your other question, "<dev>" is just shorthand for
"<insert whatever device your filesystem is on here>". i.e.
/dev/centos/root in this case...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2021-09-09 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 14:35 Repair Metadata corruption detected at xfs_inode_buf_verify on CentOS 7 virtual machine brian
2021-09-08 21:39 ` Dave Chinner
2021-09-08 23:08 ` brian
2021-09-09 2:54 ` Dave Chinner
2021-09-09 3:39 ` brian
2021-09-09 19:11 ` brian
2021-09-09 21:09 ` Dave Chinner [this message]
2021-09-10 3:26 ` brian
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=20210909210951.GD2361455@dread.disaster.area \
--to=david@fromorbit.com \
--cc=a001@yakkadesign.com \
--cc=linux-xfs@vger.kernel.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