Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 1.8.x (1.8.0 - 1.8.5)
-
None
-
sles10sp3, sles11sp1, centos5.6, centos6
-
3
-
21,812
-
5412
Description
"NASA/AMES is asking for the ability to be able to tell users which files may be suspect after an
adverse cluster event; panics, hangs, client evictions, etc.
One example that may be easier than others is when a client is evicted and the client is forced to
toss dirty pages of open files. The site has been experimenting with a way to list the inode
numbers on the mds with the associated pages tossed on the clients. I'll leave it to them to
discuss here.
" – from Oracle BZ 21812.
Oracle has released a patch (attachment 33114.) It affected client side. We like Whamcloud to include this patch for 1.8.x and 2.1.x.
Attachments
Issue Links
- is related to
-
LU-2505 lfsck: BUG: soft lockup - CPU#0 stuck for 67s! [umount:22194]
- Resolved
- Trackbacks
-
Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA