I suspect the OST that hosts the file is not mounted. What does lctl dl
gives you on a client?
Murshid.
On Fri, Mar 10, 2017 at 5:19 PM Gibbins, Faye
wrote:
> Hi,
>
>
>
> One of the directories on my lustre file system is showing up like this
> when I do an ‘ls -l’ on its parent directory.
>
>
Hi,
-2 is ENOENT The requested file or directory does not exist
-11 is EAGAIN Try again
-95 is EOPNOTSUPP Operation not supported on transport endpoint
-116 is ESTALE Stale file handle
We've had this issue when we were running 2.5.3. Didn't seem to be giving
us any problems so we've updated lustr
We've been doing writeconf as a workaround for this. We're running 2.5.3
Hope this helps.
Murshid.
On Aug 24, 2016 2:06 AM, "Jessica Otey" wrote:
> All,
> This is a bit of a complex scenario but I am hoping that someone out there
> can provide some relevant experience.
>
> We have a production
Hello Lustre gurus,
Recently, one of our OSS' had a faulty RAID card (3ware) and this has
corrupted the root filesystem and Lustre OST.
We then reinstalled the OS, fsck'd Lustre OST using a backup superblock
(the primary one was corrupted) and recreated the journal (journal also
corrupted). We no
On the oss. lctl --device abort_recovery. Hope that helps.
Murshid.
On Sun, Jun 7, 2015, 18:49 Kurt Strosahl wrote:
> Hello,
>
> We had a lustre oss that had to be rebooted, and one of its osts has
> now been in recovery mode for almost 12 hours. It is working though its
> list of clients
I faced the same problem previously, running writeconf sorted it out for me.
Murshid.
On Wednesday, November 26, 2014, Jon Tegner wrote:
> Hi!
>
> I recently got some help regarding removing an OSS/OST from the file
> system. Last thing I did was to permanently remove it with (on the MDS):
>
>
rinted and we know what is the call path.
>
> Bye,
> Oleg
> On Aug 26, 2014, at 12:28 AM, Murshid Azman wrote:
>
> > Hello Oleg,
> >
> > Thanks for your response.
> >
> > The kernel I'm using is 2.6.32-279.19.1.el6.x86_64
> >
> > This c
FilesystemSize Used Avail Use% Mounted on
tmpfs 50M 484K 50M 1% /
I've removed the NFS mounts but can still see the same error. This client
does not share NFS to others.
Thank you.
Murshid Azman.
On Fri, Aug 22, 2014 at 9:12 PM, Drokin, Oleg wrote:
> He
ext in it?
>
> If so, one of the funnier Lustre error messages to be sure.
>
> --Jeff
>
>
> On Fri, Aug 22, 2014 at 12:28 AM, Murshid Azman
> wrote:
>
>> Hello Everyone,
>>
>> We're trying to run a cluster image on Lustre filesystem version 2.5.2
>&
Tell Peter, lookup on mtpt, it open
2014-08-22T13:52:01+07:00 node01 kernel: LustreError:
4271:0:(namei.c:530:ll_lookup_it()) Skipped 128 previous similar messages
This doesn't happen to our desktop Lustre clients.
I'm wondering if anyone has any idea what this means.
T
ink a writeconf is required on all servers and
clients
http://wiki.lustre.org/manual/LustreManual20_HTML/LustreMaintenance.html#50438199_54623.
Do you foresee any problems running this on our production system?
I'm running Lustre 2.5.0 on servers and clients.
T
11 matches
Mail list logo
