Subject: Re: Large inodes for ffs
To: None <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 03/23/1999 13:49:25
On Tue, 23 Mar 1999 13:25:42 -0800 (PST)
Paul Goyette <firstname.lastname@example.org> wrote:
> Is the vnextops interface going to be sufficiently general to store
> (pointers to) arbitrarily large amounts of "opaque data" per file?
> Where would this info be stored, in "continuation inodes"?
If an application (say, a layered FS) wanted to store additional
opaque data, perhaps it allocates a new file, and stores a pointer
(via inode number) to it. Userland applications could do this as
Really, vnextops is orthogonal to the opaque data storage. It's being
used in the upper layer that Bill is working on (a data migration layer)
for other things. Hence the separated "generic" vs. "fs specific" namespace.
-- Jason R. Thorpe <email@example.com>