Hi All,
Issue : Logs are continuously generating oin lustre clients while
accessing the luster file system by user.
Logs entry: LustreError:
5848:0:(file.c:3280:ll_inode_revalidate_fini()) failure -43 inode
176619521
As mentioned in manual guide, we need to update UID/GID on the MDS node
As in there are some different patches in our 1.8.7-wc1 release than in
Oracle's 1.8.7 release, because we made our 1.8.7-wc1 release on Oct 31, 3
months after our 1.8.6-wc1 release, but Oracle just tagged their 1.8.7
release this week.
We do monitor each others releases to keep the
Dennis
If you have questions about Whamcloud Lustre releases then wc-discuss is
the appropriate place to ask them.
Regards
Peter
On 12-01-19 8:00 AM, Charland, Denis wrote:
As in there are some different patches in our 1.8.7-wc1 release than in
Oracle's 1.8.7 release, because we made our
Hello!
On Jan 17, 2012, at 3:26 AM, Lai Siyao wrote:
Are you referring to ll_lookup_it_finish() that flag negative dentry
DCACHE_LUSTRE_INVALID and hash/unhash it immediately if client doesn't have
UDATE lock? Looks like such dentry is skipped during link path walk as
ll_dcompare checks
