[LU-4157] Removing files hangs with 100%CPU on 3.12-rc7 client Created: 28/Oct/13 Updated: 27/Dec/13 Resolved: 27/Nov/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Roland Fehrenbacher | Assignee: | WC Triage |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Vanilla kernel 3.12-rc7 client mounting a 2.4.1 ZFS server that works fine with a 2.4.1 client. |
||
| Issue Links: |
|
||||||||
| Severity: | 4 | ||||||||
| Rank (Obsolete): | 11279 | ||||||||
| Description |
|
Deleting files with the in-kernel client (3.12-rc7) is impossible. The rm command gets stuck at 100%CPU and is unkillable with an example call trace like the following: Oct 23 15:49:05 beo-05 kernel: [ 1361.539903] [<ffffffff815020ff>] ? __schedule+0x2ff/0x8d0 |
| Comments |
| Comment by Peng Tao [ 30/Oct/13 ] |
|
It it the same hang I fixed before. The patch is queued by Greg KH in staging tree but not yet in Linus tree. The root cause is because of a generic layer change that makes truncate_inode_pages_range stop truncating the page at index ~0UL but Lustre always put the first page in a dir inode mapping at index ~0UL. See the patch for details https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/commit/?h=staging-next&id=363090e74f3865c589f4026b40865596b0212f90 |
| Comment by Roland Fehrenbacher [ 01/Nov/13 ] |
|
Thanks Peng. I applied the patch and it fixes the problem indeed. Would be great if it could move to 3.12 final (together with the patch in https://jira.hpdd.intel.com/browse/LU-4127 maybe?). |
| Comment by Peng Tao [ 01/Nov/13 ] |
|
The two patches are both queue by Greg in his staging-next branch but I do not know when he will push them to Linus. |
| Comment by Roland Fehrenbacher [ 02/Nov/13 ] |
|
OK, thanks for letting me know. I assume this will go into a 3.12.x then. Without these patches, the lustre client is absolutely useless. |
| Comment by Dmitry Eremin (Inactive) [ 27/Nov/13 ] |
|
It's fixed in upstream. |