Hello,
I have a important question for my infrastructure. I have a
lustre-filesystem with 300TBytes. A aplication mount a subdirectory with
bind option and user quotas. This user only own 100TBytes configured
with lustre quotas, but when report the free space show 300TBytes.
is it possible show
Hi list,
if a Lustre router is down, comes back to life and the servers do not
actively test the routers periodically: is it possible to mark a Lustre
router as up? Or to tell the servers to ping the router?
Or can I enable the router pinger in a live system without unloading
and loading the
I've found that even with the Protocal Error, it still works.
-Jason
-Original Message-
From: lustre-discuss-boun...@lists.lustre.org
[mailto:lustre-discuss-boun...@lists.lustre.org] On Behalf Of Michael Shuey
Sent: martedì, 25. gennaio 2011 14:45
To: Michael Kluge
Cc: Lustre
On Tue, 2011-01-25 at 10:00 +0100, Alfonso Pardo wrote:
Hello,
Hi,
I have a
lustre-filesystem with 300TBytes. A aplication mount a subdirectory with
bind option and user quotas. This user only own 100TBytes configured
with lustre quotas,
Do you mean that a given user has a quota limit of
Hi, no response on this the first time I sent it around. Can anyone
help me on this?
Thanks,
bob
Original Message
Subject:
[Lustre-discuss] question about routing between subnets
Jason, Michael,
thanks y lot for your replies. I pinged everone from all directions but
the router is still marked down on the client. I even removed and
re-added the router entry via lctl --net tcp1 del_route xyz@o2ib and
lctl --net tcp1 add_route xyz@o2ib . No luck. So I think I'll wait for
the
OK, so, finally with time on my hands, I find I can make this work.
Sorry about the message list traffic.
bob
On 1/25/2011 9:51 AM, Bob Ball wrote:
Hi, no response on this the first time I sent it around. Can
anyone help me on this?
The MGS can be behind an lnet router. So, provided you have LNET routing set
up between
A and B, the MGS should be okay with only a subnet A address, clients on B
with proper
routing configuration should be fine.
The address on net C is thus immaterial.
cliffw
On Tue, Jan 25, 2011 at 6:51 AM,
I have one lustre client that keeps reporting the following error.
Jan 25 09:43:07 edclxs11 kernel: LustreError:
6886:0:(file.c:3287:ll_inode_revalidate_fini()) failure -2 inode 202278709
Jan 25 09:43:07 edclxs11 kernel: LustreError:
6886:0:(file.c:3287:ll_inode_revalidate_fini()) Skipped 7
Hello!
It's not necessary missing, some other factors might be in play. E.g. if you
have somewhat older version of Lustre and export it via NFS from this node,
I think there was a bug leading to such messages.
If it is indeed missing, e2fsck should fix a case where a directory entry
Though I think its marked as development or experimental in the Lustre
documention or source lctl set_route has worked fine for me in the past
with no issues.
lctl set_route nid up
is the syntax I believe.
Jeremy
On Tue, Jan 25, 2011 at 9:52 AM, Michael Kluge
michael.kl...@tu-dresden.dewrote:
On Fri, Jan 21, 2011 at 1:02 PM, Andreas Dilger adil...@whamcloud.comwrote:
On 2011-01-21, at 06:55, Ben Evans wrote:
In our lab, we've never had a problem with simply having 1 MGS per
filesystem. Mountpoints will be unique for all of them, but functionally it
works just fine.
While this
it worked ... but the issue went away as well.
Professor Samuel Aparicio BM BCh PhD FRCPath
Nan and Lorraine Robertson Chair UBC/BC Cancer Agency
675 West 10th, Vancouver V5Z 1L3, Canada.
office: +1 604 675 8200 cellphone: +1 604 762 5178: lab website
http://molonc.bccrc.ca
PLEASE SUPPORT MY
Hi Jeremy,
yup, it's marked obsolete (DANGEROUS) , whatever, it did the
trick :)
Thanks a lot, Michael
Am Dienstag, den 25.01.2011, 18:55 -0500 schrieb Jeremy Filizetti:
Though I think its marked as development or experimental in the Lustre
documention or source lctl set_route
14 matches
Mail list logo
