From: Laurent Barbe <laurent@ksperis.com>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: krbd & live resize
Date: Tue, 30 Jul 2013 11:55:00 +0200 [thread overview]
Message-ID: <51F78D74.803@ksperis.com> (raw)
In-Reply-To: <51F6E389.1040607@dachary.org>
Hello Loic,
which version of kernel do you use for krbd ?
Laurent
Le 29/07/2013 23:50, Loic Dachary a écrit :
> Hi,
>
> This works:
>
> lvcreate --name tmp --size 10G all
> Logical volume "tmp" created
> mkfs.ext4 /dev/all/tmp
> mount /dev/all/tmp /mnt
> blockdev --getsize64 /dev/all/tmp
> 10737418240
> lvextend -L+1G /dev/all/tmp
> Extending logical volume tmp to 11,00 GiB
> Logical volume tmp successfully resized
> blockdev --getsize64 /dev/all/tmp
> 11811160064
> resize2fs /dev/all/tmp
> resize2fs 1.41.12 (17-May-2010)
> Filesystem at /dev/all/tmp is mounted on /mnt; on-line resizing required
> old desc_blocks = 1, new_desc_blocks = 1
> Performing an on-line resize of /dev/all/tmp to 2883584 (4k) blocks.
> The filesystem on /dev/all/tmp is now 2883584 blocks long.
>
> This does not work:
>
> rbd create --size 10240 tmp
> rbd info tmp
> rbd image 'tmp':
> size 10240 MB in 2560 objects
> order 22 (4096 KB objects)
> block_name_prefix: rb.0.12dd.238e1f29
> format: 1
> rbd map tmp
> mkfs.ext4 /dev/rbd1
> mount /dev/rbd1 /mnt
> blockdev --getsize64 /dev/rbd1
> 10737418240
> rbd resize --size 20000 tmp
> blockdev --getsize64 /dev/rbd1
> 10737418240
> resize2fs /dev/rbd1
> resize2fs 1.42 (29-Nov-2011)
> The filesystem is already 2621440 blocks long. Nothing to do!
>
> It does work after umounting:
>
> umount /mnt
> blockdev --getsize64 /dev/rbd1
> fsck -f /dev/rbd1
> resize2fs /dev/rbd1
> resize2fs 1.42 (29-Nov-2011)
> Resizing the filesystem on /dev/rbd1 to 5120000 (4k) blocks.
> The filesystem on /dev/rbd1 is now 5120000 blocks long.
>
> I assume there should be "something" in KRBD to allow for the same behavior as with LVM but I don't know enough about the kernel to be more specific. Maybe something similar to ioctl BLKRRPART ?
>
> Cheers
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-07-30 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 21:50 krbd & live resize Loic Dachary
2013-07-30 9:55 ` Laurent Barbe [this message]
2013-07-30 9:57 ` Loic Dachary
2013-07-30 10:03 ` Loic Dachary
2013-07-30 10:07 ` Laurent Barbe
2013-07-30 11:01 ` Loic Dachary
2013-07-30 13:40 ` Loic Dachary
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=51F78D74.803@ksperis.com \
--to=laurent@ksperis.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.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.