From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Using cwfs
Date: Sun, 23 Aug 2009 21:45:17 -0400 [thread overview]
Message-ID: <fe41879c0908231845i68474e3dud9721725263fa20b@mail.gmail.com> (raw)
In-Reply-To: <fe41879c0908231305v4cba24c1ue48ba1dd104ff59e@mail.gmail.com>
I'll use this thread to post further questions about cwfs.
I recently had a problem accessing a directory in a
drive managed by cwfs - whenever I tried to access
the dir, I got the error:
...: phase error -- cannot happen
so I went over to the cwfs console and played around
with `clean':
fs: clean /path/to/trouble
dblock[0] = 286843
dblock[1] = 0
...
iblocks[6] = 0
...
fs: clean /path/to/trouble 286843
... (see above)
fs: clean /path/to/trouble 0
dblock[0] = 286843
dblock[0] modified 0
dblock[1] = 0
...
fs: clean /path/to/trouble
dblock[0] = 0
...
at this point, "uh oh," I thought. I could access
the directory, but of course all files inside were
no longer accessible - just me playing around
a bit. There used to be a 1G file in there; I hope
I can still access it through the worm dump.
I subsequently performed an `rm /path/to/trouble'.
Anyways, a `check rdall' reveals
nmiss = 189296
is this something I should be worried about?
Is the rest of that data inside the directory I
performed a clean 0 on, still dangling somewhere
in the FS, that it should be wiped out? The `check'
shows
nbad = 0
nqbad = 0
but the large number of nmiss still holds my attention.
Best,
ak
next prev parent reply other threads:[~2009-08-24 1:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-23 7:37 Akshat Kumar
2009-08-23 12:54 ` erik quanstrom
2009-08-23 13:07 ` Anthony Sorace
2009-08-23 20:05 ` Akshat Kumar
2009-08-24 1:45 ` Akshat Kumar [this message]
2009-08-24 2:11 ` Akshat Kumar
2009-08-24 3:27 ` erik quanstrom
2009-08-24 3:53 ` Akshat Kumar
2009-08-24 11:10 ` Mathieu L.
2009-08-25 20:55 ` erik quanstrom
2009-08-24 20:38 ` Akshat Kumar
2009-08-24 22:13 ` cinap_lenrek
2009-08-25 20:56 ` erik quanstrom
2009-08-27 1:24 ` Akshat Kumar
2009-08-27 3:29 ` erik quanstrom
2009-08-27 14:09 ` Francisco J Ballesteros
2009-08-27 14:16 ` erik quanstrom
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=fe41879c0908231845i68474e3dud9721725263fa20b@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/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).