[Lustre-community] Error on a specifc lustre directory

[Alfonso Pardo]

Hello to everyone,

 

I have a lustre file system (servers and cliente with lustre 2.3). The filesystem work fine, but the files of a specific directory I can’t access to the files.

 

For example this files has the next atributes from a client:

 

[root@login-hpc-02 ~]# lfs osts

OBDS::

0: cetafs-OST0000_UUID ACTIVE

1: cetafs-OST0001_UUID ACTIVE

2: cetafs-OST0002_UUID ACTIVE

3: cetafs-OST0003_UUID ACTIVE

4: cetafs-OST0004_UUID ACTIVE

5: cetafs-OST0005_UUID ACTIVE

6: cetafs-OST0006_UUID ACTIVE

7: cetafs-OST0007_UUID ACTIVE

8: cetafs-OST0008_UUID ACTIVE

9: cetafs-OST0009_UUID ACTIVE

10: cetafs-OST000a_UUID ACTIVE

11: cetafs-OST000b_UUID ACTIVE

12: cetafs-OST000c_UUID ACTIVE

13: cetafs-OST000d_UUID ACTIVE

14: cetafs-OST000e_UUID ACTIVE

15: cetafs-OST000f_UUID ACTIVE

16: cetafs-OST0010_UUID ACTIVE

17: cetafs-OST0011_UUID ACTIVE

18: cetafs-OST0012_UUID ACTIVE

19: cetafs-OST0013_UUID ACTIVE

21: cetafs-OST0015_UUID ACTIVE

22: cetafs-OST0016_UUID ACTIVE

23: cetafs-OST0017_UUID ACTIVE

24: cetafs-OST0018_UUID ACTIVE

[root@login-hpc-02 ~]# lfs getstripe /mnt/data/psf_660__769_676_.psf

/mnt/data/psf_660__769_676_.psf

lmm_stripe_count:   18

lmm_stripe_size:    1048576

lmm_layout_gen:     0

lmm_stripe_offset:  0

        obdidx           objid          objid            group

             0         4463291       0x441abb                0

             2         4463099       0x4419fb                0

             4         4462606       0x44180e                0

             6         4462843       0x4418fb                0

             8         4463190       0x441a56                0

             9         4462363       0x44171b                0

            12         4463003       0x44199b                0

            14         4465177       0x442219                0

            16         4463883       0x441d0b                0

             1         4463701       0x441c55                0

             3         4462395       0x44173b                0

             5         4462747       0x44189b                0

             7         4463387       0x441b1b                0

            10         4462646       0x441836                0

            11         4462267       0x4416bb                0

            13         4462491       0x44179b                0

            15         4463515       0x441b9b                0

            17         4465387       0x4422eb                0

 

 

But if I try to access or delete I only get:

 

ls: cannot access hubble_psf_660__691_555_.psf: Interrupted system call

 

or if I try to delete:

 

rm: cannot access hubble_psf_660__691_555_.psf: Interrupted system call

 

 

Any suggestions to access or delete the files?

 

 

Thanks in advance

Alfonso Pardo Díaz
Researcher / System Administrator at CETA-Ciemat
c/ Sola nº 1; 10200 Trujillo, ESPAÑA
Tel: +34 927 65 93 17 Fax: +34 927 32 32 37

---------------------------- Confidencialidad: Este mensaje y sus ficheros adjuntos se dirige exclusivamente a su destinatario y puede contener informaci�n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci�n, divulgaci�n y/o copia sin autorizaci�n est� prohibida en virtud de la legislaci�n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente respondiendo al mensaje y proceda a su destrucci�n. Disclaimer: This message and its attached files is intended exclusively for its recipients and may contain confidential information. If you received this e-mail in error you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited and may be unlawful. In this case, please notify us by a reply and delete this email and its contents immediately. ----------------------------

[Drokin, Oleg]

Hello!

On Apr 9, 2013, at 4:02 AM, Alfonso Pardo wrote:

> But if I try to access or delete I only get:
>
> ls: cannot access hubble_psf_660__691_555_.psf: Interrupted system call
>
> or if I try to delete:
>
> rm: cannot access hubble_psf_660__691_555_.psf: Interrupted system call

Does it fail right away, or after some waiting?
Anything interesting you see in dmesg after that?
If not, perhaps try to capture a lustre log of the operation at some extended log level and see if there are any clues there?

Bye,
Oleg
_______________________________________________
Lustre-community mailing list
Lustre-c...@lists.lustre.org
http://lists.lustre.org/mailman/listinfo/lustre-community