From: "dan1" <dan1@edenpics.com>
To: linux-raid@vger.kernel.org
Subject: mdadm grow size gives device or resource busy error
Date: Fri, 11 Jan 2013 23:55:46 +0100 [thread overview]
Message-ID: <BE5C56FCE65D44E28D3E1EC53ABC7BC3@home> (raw)
Hi,
I am trying to shrink an md partition to lower its size but that fails with
an error message.
My context is the following:
/dev/md2 has 3 partitions: /dev/sdb3; /dev/sdc3; /dev/sdd3
The array is 480 Gbytes big (only 30 Gbytes used).
I want to resize it to 100Gbytes (hosting company only allows that size).
Following a procedure, I first resize the partition to 70Gbytes to let some
space:
umount /dev/md2
e2fsck /dev/md2
resize2fs /dev/md2 70G
Then, I disable the bitmap:
mdadm --grow /dev/md2 --bitmap none
And I shrink the array to 100Gbytes (201x512x1024):
mdadm --grow /dev/md2 --size=105381888
Doing this, it produces the following error message:
mdadm: Cannot set size on array members.
mdadm: Cannot set device size for /dev/md2: Device or resource busy
If I look at the messages with "dmesg | tail" there is no error message due
to that manipulation.
Some things to check:
1. No rebuild is in progress (with cat /proc/mdstat): OK
2. The array is unmounted: OK
3. The proble doesn't come from the bitmap as it has been disabled before.
OK
4. Opened files related to the md2 device are the following:
lsof | grep md2
md2_raid1 403 root cwd DIR 9,91 4096 2 /
md2_raid1 403 root rtd DIR 9,91 4096 2 /
md2_raid1 403 root txt unknown /
proc/403/exe
I don't know if this is ok or not but I assume it is fine as I didn't mount
the array and didn't put any file on it in this session.
The versions of my system are the following:
Linux CentOS 6.3
mdadm V3.2.3
Thanks for any help.
Daniel
next reply other threads:[~2013-01-11 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 22:55 dan1 [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-15 21:09 mdadm grow size gives device or resource busy error dan1
[not found] ` <CAANkY-=ZDA1y4fTmZSw_X4EbD_XfsVVH_hUd5RWL1pTcv1OYiA@mail.gmail.com>
2013-01-23 21:35 ` dan1
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=BE5C56FCE65D44E28D3E1EC53ABC7BC3@home \
--to=dan1@edenpics.com \
--cc=linux-raid@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