Messages in this thread | | | Date | Sat, 6 Jan 2001 06:08:46 +0100 | From | Stefan Traby <> | Subject | Re: ramfs problem... (unlink of sparse file in "D" state) |
| |
On Fri, Jan 05, 2001 at 11:52:31PM -0500, Alexander Viro wrote: > On Sat, 6 Jan 2001, Stefan Traby wrote: > > > Then I tried to unlink the file by running rm lfs.file log. > > > > The rm process (and an ls process that I started after that) > > are now in "D" state... > > > > root 2934 0.0 0.2 1292 452 pts/5 D 05:38 0:00 ls /ramfs > > root 2952 0.0 1.5 4028 2384 pts/3 S 05:40 0:00 vi sdlkhfd > > Add UnlockPage(page) at the end of ramfs_writepage().
Shit. You are quite fast. Works.
It was the first D-state case here where sync(1) did not fall into D-state, too. (ok, I know why :)
--
Stefan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |