| To: | linux-xfs <linux-xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: open unlinked logs (was Re: losing disk space) |
| From: | Jason White <jasonw@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Date: | Sat, 27 Mar 2004 14:52:35 +1100 |
| In-reply-to: | <Pine.LNX.4.44.0403262055150.20191-100000@xxxxxxxxxxxxxxxxxxxxxx> |
| References: | <16484.50274.645339.623409@xxxxxxxxx> <Pine.LNX.4.44.0403262055150.20191-100000@xxxxxxxxxxxxxxxxxxxxxx> |
| Reply-to: | jasonw@xxxxxxxxxxxxxxxxxxxxxxxx |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
Eric Sandeen writes: > nothing wrong with unlinking open files, they just hang > around to some extent until they're closed. I don't think > it's anything to worry about, although it might be odd that > something is holding it open after deletion for a very long > time... What is pid 380? cupsd I just thought that as what xfs_repair recovered a few weeks ago was also a cups log file that there might be a connection between log files' being held open after deletion, and the disconnected inode on that occasion (xfs_repair was run after a power failure and after xfs recovery). From the original report by Greg Koch it appears there were disconnected inodes in that case too, though we don't know yet whether files were being held open after unlinking. There might be nothing in any of this, of course. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: open unlinked logs (was Re: losing disk space), Eric Sandeen |
|---|---|
| Next by Date: | [Bug 322] xfs internal error, bugzilla-daemon |
| Previous by Thread: | Re: open unlinked logs (was Re: losing disk space), Eric Sandeen |
| Next by Thread: | Re: losing disk space, Greg Koch |
| Indexes: | [Date] [Thread] [Top] [All Lists] |