So we have a new file system set up. beefy OSTs, but certainly under- sized metadata (we're still figuring out what we'll use in the end). We've just started to do friendly-user testing and ran into some odd file entries. In particular: -rw-r--r-- 1 ybao esd 22317940 Jul 23 10:49 met_em.d01.2060-12-30_12:00:00.nc ?--------- ? ? ? ? ? met_em.d01.2060-F9?q -rw-r--r-- 1 ybao esd 22317940 Jul 23 14:30 met_em.d01.2061-01-01_18:00:00.nc
This seems to not only be an odd file entry, but might be messing with proper wildcard listings. For instance: [r...@n0000 GFDLMET1]# ls met_em.d01.2060-01-01* ls: met_em.d01.2060-01-01*: No such file or directory [r...@n0000 GFDLMET1]# ls met_em.d01.2060-01-01_00:00:00.nc met_em.d01.2060-01-01_00:00:00.nc [r...@n0000 GFDLMET1]# Does anyone know a possible cause for this? I'm not convinced this wasn't just a poorly executed transfer on the user's part, but I would expect a file entry to still contain proper owner metadata, etc. ---------------- John White High Performance Computing Services (HPCS) (510) 486-7307 One Cyclotron Rd, MS: 50B-3209C Lawrence Berkeley National Lab Berkeley, CA 94720 _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
