[9fans] file systems

[9fans] file systems

[Joel Salomon]

> as simple as inode/superblock/indirect block fs's go
Speaking of which, how do I find out how the kfs is laid
out on disk?

--Joel

Re: [9fans] file systems

[Fco.J.Ballesteros]

[-- Attachment #1: Type: text/plain, Size: 189 bytes --]

/sys/src/cmd/disk/kfs/portdat.h has the data structures.
Look for `don't touch, this is the disk structure' warnings.

You could also follow the trace resulting from a check call.

hth

[-- Attachment #2: Type: message/rfc822, Size: 1481 bytes --]

From: Joel Salomon <salomo3@cooper.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] file systems
Date: Mon, 24 Feb 2003 14:29:16 -0500 (EST)
Message-ID: <Pine.SOL.3.96.1030224142637.17571B-100000@robin.cooper.edu>

> as simple as inode/superblock/indirect block fs's go
Speaking of which, how do I find out how the kfs is laid
out on disk?

--Joel

Re: [9fans] file systems

[Geoff Collyer]

`The Plan 9 File Server' (in /sys/doc/fs) describes how the pre-fossil
standalone file server stores data on disks.  kfs is a slight variant
of the non-cached-worm file system.  The main change I noticed when
adapting a private copy of kfs to read standalone file systems was
that struct Superb swaps the order of its members, a Super1 and an
Fbuf, to permit the size of the free list in Fbuf to vary with block
size, which can be chosen at run-time in kfs, but which is fixed at
compile-time in the standalone file server.

Re: [9fans] file systems

[Russ Cox]

the EXAMPLES section of 9p(2) gives some suggestions.