Hi list
After digging deeper on our mds and osts log, i found that maybe i had a
problem with *last_id and obdid*. I checked follow the instruction in the
lustre 1.8 manual ( 821-0035 v1.3 - 23.3.9 ) and saw that the last_id
matched with the object existing on my OST and that means the problem is
Andreas,
Yes, these I/O errors are for any NFS filesystems mounted on all lustre
clients. Even though this nfs mount has nothing to do with lustre there
seems to be something specific on the lustre clients with the kernel-ib and
lustre client modules installed that seems to be causing this proble
On 2010-08-08, at 16:44, Jagga Soorma wrote:
> One other piece of information. It seems like I have found a workaround by
> adding a cronjob that runs every 2mins and runs a df command. Is there some
> caching issue that might be caused by lustre?
Are the IO errors on NFS filesystems that have
One other piece of information. It seems like I have found a workaround by
adding a cronjob that runs every 2mins and runs a df command. Is there some
caching issue that might be caused by lustre?
Thanks,
-J
On Sun, Aug 8, 2010 at 3:15 AM, Jagga Soorma wrote:
> Hello,
>
> I am experiencing so
Hi,
We have a customer that is down right now, and is not able to run jobs.
The file systems that was up and running fine for weeks. Then, on 8/1, one of
the OSTs was having IB problems. I unmounted the OST, fixed the IB problem
(reseated the cable), then tried mounting the OST, but the mount
Hello,
I am experiencing some weird behavior on my lustre clients. I have worked
with Novell support and they keeping pointing to lustre as the culprit for
these issues. I am getting intermittent I/O errors when running df/ls on
any nfs mounts without anything being logged in syslog. After putt
