If you *really* want a block device on a client that resides in Lustre you
*could* create a file in Lustre and then make that file a loopback device
with losetup. Of course, your mileage will vary *a lot* based on use case,
access, underlying LFS configuration.
dd if=/dev/zero
On Mar 16, 2023, at 04:50, Passerini Marco
mailto:marco.passer...@cscs.ch>> wrote:
By trial and error, I found that, when using project quotas, the maximum ID
available is 4294967294. Is this correct?
Yes, the "-1" ID is reserved for error conditions.
If I assign quota to a lot of project
Are you asking if you can mount Lustre on a client so that it shows up as a
block device? If so, the answer to that is you can't. Lustre does not appear
as a block device to the clients.
-Rick
On 3/16/23, 3:44 PM, "lustre-discuss on behalf of Shambhu Raje via
lustre-discuss"
Lustre doesn't show up in lsblk on the client because it isn't a block device
on the client. NFS and other network file systems also don't show up lsblk,
for the same reason.
-Patrick
From: lustre-discuss on behalf of
Shambhu Raje via lustre-discuss
Sent:
When we mount a lustre file system on client, the lustre file system does
not use block device on client side. Instead it uses virtual file system
namespace. Mounting point will not be shown when we do 'lsblk'. As it only
show on 'df-hT'.
How can we mount lustre file system on block such that
Thank you for the clarification.
On Thu, Mar 16, 2023, 01:36 Laura Hild wrote:
> Hi Shambhu-
>
> I believe neither the ldiskfs nor ZFS OSDs support an active-active
> configuration (except in the sense that one can have multiple targets, some
> of which are active on one host and others on
By trial and error, I found that, when using project quotas, the maximum ID
available is 4294967294. Is this correct?
If I assign quota to a lot of project IDs, is the performance expected to go
down more than having just a few or is it fixed?
Regards,
Marco Passerini
