From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file systems
Date: Mon, 24 Feb 2003 20:33:22 +0100 [thread overview]
Message-ID: <7d86b497d19ca0c34390bfa2c0c53c7b@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.SOL.3.96.1030224142637.17571B-100000@robin.cooper.edu>
[-- 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
next prev parent reply other threads:[~2003-02-24 19:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 19:29 Joel Salomon
2003-02-24 19:33 ` Fco.J.Ballesteros [this message]
2003-02-24 21:28 ` Geoff Collyer
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 16:52 [9fans] (no subject) Steve Simon
2003-02-24 17:38 ` [9fans] file systems Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d86b497d19ca0c34390bfa2c0c53c7b@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).