| Summary: | Error 500 during doWipeOutWorkspace | ||
|---|---|---|---|
| Product: | [Technology] Hudson | Reporter: | Dennis Huebner <dennis.huebner> |
| Component: | Core | Assignee: | Winston Prakash <winston.prakash> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, denis.roy, sebastian.zarnekow |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Dennis Huebner
From bug 363222: The .nfs0000000 etc. file represents a file that was deleted, but was still in use. The OS is just waiting for the file to no longer be used to completely remove it. -M. (In reply to comment #1) > From bug 363222: > > The .nfs0000000 etc. file represents a file that was deleted, but was still in > use. The OS is just waiting for the file to no longer be used to completely > remove it. > > -M. Can you tell which process the dangling user for the file is? > Can you tell which process the dangling user for the file is?
I've seen this same issue a couple of times last week. On both occasions it was the master Hudson process itself that was hanging onto files. I do not know why.
I am reassigning to the Hudson project for comment. This did not happen before. Hudson team: do you have any insight as to why the master process would 'hang on' to files on NFS-mounted file systems, preventing the workspace from being deleted? Dupe of bug 363652 ? *** This bug has been marked as a duplicate of bug 363652 *** |