Date: Tue, 08 Oct 2002 00:39:52 -0400 From: "David E. Cross" <crossd@cs.rpi.edu> To: bright@mu.org Cc: freebsd-fs@freebsd.org, guptar@cs.rpi.edu Subject: UFS, Inode question Message-ID: <200210080439.g984drE16529@pegasus.cs.rpi.edu>
next in thread | raw e-mail | index | archive | help
In our Journalling work we just hit a "hmmmm" point where we aren't sure if we've accounted for a certain case. That case is in the point of inode allocation.... to be specific "how (on disk) is an inode marked for allocation" Our current method independently stores inode allocation and linking as discrete events. The problem arises if one is committed without the other (think an inopportune break point in the disk-journal vs. in-core journal.) That could lead to an inode being allocated, but not actually referenced. What does the system do with an inode with a reference count of 0, is that a free inode (on the "free list"). Or can it still be an unreferenced inode? If it can be unreferenced then we need to rethink some things here as the entire point is to avoid fsck. -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210080439.g984drE16529>