To do the ll_recover_lost_found_objs, can we have everything mounted
up? Or is it recommended we unmount everything?
Also what to do when we see ? for the file attributes. Most likely
these files are gone, how can we remove them from the system all
together?
TIA
On Wed, Mar 11, 2009 at
On Mon, 2009-03-23 at 22:17 -0400, Mag Gam wrote:
Hi Brian:
Hi,
Well, there were no server problems but I did run a e2fsck on the MDT
and OST I managed to fix the corruptions (or have the e2fsck do it for
me).
There must have been some problems for fscks to have needed to fix
problems.
So
If I have 5 clients, two of which are running an app which requires fcntl
style file locking, do I need to mount lustre with -o flock on all five
clients, or just the two that are using fcntl?
What are the implications (if any) of mounting a lustre filesystem with -o
flock?
Thanks!
Jay
Hello,
Following the procedure outlined in the Lustre Manual Chapter 15 on
backup and restore, I have tried two approaches to backing up a single
MDT disk. One was the getfattr and then tar -cvf to get the data and
restore it via the tar -xvf and setfattr method. The other method
was the rsync
Hello;
Is Lustre supported on SLES 11? If not, when will it be supported? Also, what
version of OFED will it support? SLES 11 comes with OFED 1.4, since there are
issues getting Lustre to work with it; will that require downgrading to OFED
1.3.1?
Thanks.
Abdel..
Hi,
I have encountered an issue with Lustre that has happened a couple of times
now. I am beginning to suspect an issue with the IB fabric but wanted to
reach out to the list to confirm my suspicions. The odd part is that even
when the MDS complains that it cannot connect to a given ost, lctl
Hello!
On Mar 24, 2009, at 3:19 PM, Jay Christopherson wrote:
If I have 5 clients, two of which are running an app which requires
fcntl style file locking, do I need to mount lustre with -o flock on
all five clients, or just the two that are using fcntl?
Just two would be fine.
What
