I don't know Marc, i only know what I had to do to get the thing
working :-)
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
is that the RBD Image needs to have a partition entry
> created for it - that might be "obvious" to some, but my ongoing belief
> is that most "obvious" things aren't, so its better to be explicit about
> such things.
> >
Are you absolutely sure about this? I think you are missing something
Hi All,
OK, an update for everyone, a note about some (what I believe to be)
missing information in the Ceph Doco, a success story, and an admission
on my part that I may have left out some important information.
So to start with, I finally got everything working - I now have my 4T
RBD
Hi,
March 24, 2024 at 8:19 AM, "duluxoz" wrote:
>
> Hi,
>
> Yeah, I've been testing various configurations since I sent my last
>
> email - all to no avail.
>
> So I'm back to the start with a brand new 4T image which is rbdmapped to
>
> /dev/rbd0.
>
> Its not formatted (yet) and so not
I suspect this may be a network / firewall issue between the client and one
OSD-server. Perhaps the 100MB RBD didn't have an object mapped to a PG with
the primary on this problematic OSD host but the 2TB RBD does. Just a
theory.
Respectfully,
*Wes Dillingham*
LinkedIn
Hi Alexander,
Already set (and confirmed by running the command again) - no good, I'm
afraid.
So I just restart with a brand new image and ran the following commands
on the ceph cluster and the host respectively. Results are below:
On the ceph cluster:
[code]
rbd create --size 4T
Hello Matthew,
Is the overwrite enabled in the erasure-coded pool? If not, here is
how to fix it:
ceph osd pool set my_pool.data allow_ec_overwrites true
On Mon, Mar 25, 2024 at 11:17 AM duluxoz wrote:
>
> Hi Curt,
>
> Blockdev --getbsz: 4096
>
> Rbd info my_pool.meta/my_image:
>
> ~~~
>
> rbd
Hi Curt,
Blockdev --getbsz: 4096
Rbd info my_pool.meta/my_image:
~~~
rbd image 'my_image':
size 4 TiB in 1048576 objects
order 22 (4 MiB objects)
snapshot_count: 0
id: 294519bf21a1af
data_pool: my_pool.data
block_name_prefix:
Hi, Alwin,
Command (as requested): rbd create --size 4T my_pool.meta/my_image
--data-pool my_pool.data --image-feature exclusive-lock --image-feature
deep-flatten --image-feature fast-diff --image-feature layering
--image-feature object-map --image-feature data-pool
On 24/03/2024 22:53,
Hey Mathew,
One more thing out of curiosity can you send the output of blockdev
--getbsz on the rbd dev and rbd info?
I'm using 16TB rbd images without issue, but I haven't updated to reef .2
yet.
Cheers,
Curt
On Sun, 24 Mar 2024, 11:12 duluxoz, wrote:
> Hi Curt,
>
> Nope, no dropped
Hi Curt,
Nope, no dropped packets or errors - sorry, wrong tree :-)
Thanks for chiming in.
On 24/03/2024 20:01, Curt wrote:
I may be barking up the wrong tree, but if you run ip -s link show
yourNicID on this server or your OSDs do you see any
errors/dropped/missed?
I may be barking up the wrong tree, but if you run ip -s link show
yourNicID on this server or your OSDs do you see any errors/dropped/missed?
On Sun, 24 Mar 2024, 09:20 duluxoz, wrote:
> Hi,
>
> Yeah, I've been testing various configurations since I sent my last
> email - all to no avail.
>
>
Hi,
Yeah, I've been testing various configurations since I sent my last
email - all to no avail.
So I'm back to the start with a brand new 4T image which is rbdmapped to
/dev/rbd0.
Its not formatted (yet) and so not mounted.
Every time I attempt a mkfs.xfs /dev/rbd0 (or mkfs.xfs
Hi,
Please test again, it must have been some network issue. A 10 TB RBD
image is used here without any problems.
On Sun, Mar 24, 2024 at 1:01 PM duluxoz wrote:
>
> Hi Alexander,
>
> DOH!
>
> Thanks for pointing out my typo - I missed it, and yes, it was my
> issue. :-)
>
> New issue (sort
Hi Alexander,
DOH!
Thanks for pointing out my typo - I missed it, and yes, it was my
issue. :-)
New issue (sort of): The requirement of the new RBD Image is 2 TB in
size (its for a MariaDB Database/Data Warehouse). However, I'm getting
the following errors:
~~~
mkfs.xfs: pwrite failed:
Hello Dulux-Oz,
Please treat the RBD as a normal block device. Therefore, "mkfs" needs
to be run before mounting it.
The mistake is that you run "mkfs xfs" instead of "mkfs.xfs" (space vs
dot). And, you are not limited to xfs, feel free to use ext4 or btrfs
or any other block-based filesystem.
16 matches
Mail list logo
