Hello,
we are seeing this error a lot since we updated NFS exporting clients to 1.8.7
(oracle
version).
> Jan 16 15:19:16 xxfs1 kernel: LustreError:
> 7312:0:(file.c:3329:ll_inode_revalidate_fini()) failure -2 inode 87425037
> Jan 16 15:19:16 xxfs1 kernel: LustreError:
> 7312:0:(file.c:3329:ll
ug 16129, although that is probably not
> correct, as 16129 is the root cause, but not the solution.
>
> As we never observed it with 1.6.7.2 I didn't complain bug 19992 was closed.
> As you now can confirm it also happens with 1.6.7.2, please re-open that bug.
>
>
> Thank
Hi,
we saw this LBUG 3 times within past week, and are puzzled of what's going on,
and how comes there's no bugzilla entry for this...
What happens is that on an OSS a request (must be read or write) expects
(according to the content of the ioobj structure) to find an array of 22 struct
niobuf_re
Hello,
we see the following issue on Lustre 1.6.5.1:
Sometimes an OST mount fails with the error message
LustreError: 18644:0:(genops.c:246:class_newdev()) Device lustre-OST0003
already exists, won't add
LustreError: 18644:0:(obd_config.c:180:class_attach()) Cannot create
device lustre-OST0003
Hello,
we have a problem in a test setup where clients don't recover after a
failover of the OSS. Looking at the llog entries on the MGS I see:
#25 (224)marker 10 (flags=0x01, v1.6.5.1) lustre-OST0001 'add osc' Thu
Nov 6 17:56:23 2008-
#26 (080)add_uuid nid=10.3.0@o2ib(0x50a0300e5)
On Donnerstag 21 August 2008, Brian J. Murrell wrote:
> On Thu, 2008-08-21 at 16:40 +0200, Erich Focht wrote:
> >
> > A more general comment: what is the use of invisible bugs, anyway?
>
> You have to remember that we have customers who have sensitive data.
> Sometimes
close the company
on behalf of which the bug was reported, a mechanism for anonymizing the
reporter would make more sense. Anyway, I feel like hiding bugs is bad
in an open source project.
Regards,
Erich
On Mittwoch 20 August 2008, Brian J. Murrell wrote:
> On Wed, 2008-08-20 at 16:47 +
On Mittwoch 20 August 2008, Brian J. Murrell wrote:
> On Wed, 2008-08-20 at 16:00 +0200, Erich Focht wrote:
> > Hello,
> >
> > we're seing an LBUG on clients running with Lustre 1.6.5.1 (the servers are
> > still under 1.6.4.3). I tried finding this in bugzilla
Hello,
we're seing an LBUG on clients running with Lustre 1.6.5.1 (the servers are
still under 1.6.4.3). I tried finding this in bugzilla with no success. There
seems to be some data inconsistency, can somebody please tell me whether this
is rather on the server side (the data on disk is inconsist
On Mittwoch 18 Juni 2008, Johann Lombardi wrote:
> See bugzilla ticket 16002. The quick solution is to mount the MDT and
> to remove the CATALOGS file.
Johann, thanks very much! I need to increase my bugzilla searching
capabilities...
Best regards,
Erich
Hello,
I see the attached LBUG when trying to mount the MDT.
>From what I understand this actually means that some llog
delivers bad data. A filesystem check revealed many errors
on the MDT, and the same LBUG when trying to mount.
Is there anything I could still try to do? Remove or rewrite
confi
A related question: is there an easy way of building the Lustre kernel
RPMs for the RHEL 5.2 kernel? Maybe a bug in bugzilla with patches or so?
Thanks,
best regards,
Erich
On Freitag 13 Juni 2008, Brian J. Murrell wrote:
> On Fri, 2008-06-13 at 10:08 -0700, David Brown wrote:
> > Uhm, what happe
Thanks very much for the clarification! The improvement of the manual
as proposed by Andreas makes things easier to understand.
Best regards,
Erich
On Montag 19 Mai 2008, Nathaniel Rutman wrote:
> Erich Focht wrote:
> > Hi,
> >
> > the lustre manual says:
> >
>
Hi,
the lustre manual says:
2.2.1.5 Stopping a Server
To stop a server:
$ umount -f /mnt/test/ost0
The '-f' flag means "force"; force the server to stop WITHOUT RECOVERY.
Without the '-f' flag, "failover" is
implied, meaning the next time the server is started it goes through the
recover
Hi,
I'm puzzled by the following behavior.
An active-passive failover pair of metadata servers have separated MGS and
MDT disks and two networks (o2ib and tcp0(eth0)):
mds1: [EMAIL PROTECTED] [EMAIL PROTECTED]
mds2: [EMAIL PROTECTED] [EMAIL PROTECTED]
MGS and MDT are formatted with the options
Hi Cliff,
thanks for the answer. I guess I had a wrong picture on how this works.
Will get the system to fail over when a link breaks.
Regards,
Erich
On Dienstag 08 April 2008, Cliff White wrote:
> Erich Focht wrote:
> > Hello,
> >
> > on a setup with o2ib and ethern
Hello,
on a setup with o2ib and ethernet configured on both, lustre servers and
clients I'd expect that unplugging the infiniband cable on one of the
OSSes would lead the client to switch over to ethernet and continue I/O.
Unfortunately this doesn't happen, the client I/O stalls and continues
only
Hi,
On Dienstag 22 Januar 2008, Brian J. Murrell wrote:
> I believe new kernels have been scheduled for 1.6.5. I'm not positive
> which ones, but istr seeing new kernels patches landing for the next 1.6
> release.
I'm waiting for a RHEL5.1 client, too, and somewhat hoped it would come
along with
18 matches
Mail list logo
