Messages in this thread | | | Date | Tue, 9 Dec 2003 04:01:21 +0100 | From | Herbert Poetzl <> | Subject | Re: incorrect inode count on reiserfs |
| |
On Mon, Dec 08, 2003 at 05:24:02PM +0000, Erik Hensema wrote: > Matthias Urlichs (smurf@smurf.noris.de) wrote: > > Hi, Erik Hensema wrote: > > > >> But innwatch checks for a out-of-inodes condition. How can it differentiate > >> between a undefined number of inodes (field set to 0) and a system that ran > >> out of inodes (field dropped to 0)? > >> > > Create a file. Watch that succeed. Check whether this succeeds, and that > > the number of free inodes is still zero. > > Delete the file. Check that the number of free inodes is _still_ zero. > > > > Repeat a few times, with random sub-second delay if you're feeling > > especially paranoid today, for added confidence. > > So what hack is uglier? ;-)
hmm, well, maybe the fact that an 'inode' filesystem which ran out of inodes will not report a total of 0 inodes could help against all this uglyness ...
best, Herbert
> -- > Erik Hensema <erik@hensema.net> > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |