From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] disk/kfscmd check
Date: Sat, 17 Feb 2001 06:22:25 +0000 [thread overview]
Message-ID: <20010217062343.C5162199E6@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 54 bytes --]
man kfscmd might suggest {disk/kfscmd 'check f'}
[-- Attachment #2: Type: message/rfc822, Size: 2034 bytes --]
From: William Staniewicz <wstan@localhostnl.demon.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] disk/kfscmd check
Date: Fri, 16 Feb 2001 11:26:30 -0500
Message-ID: <20010216103020.A2923199EA@mail.cse.psu.edu>
With some reference to kfs and the 'disk/kfscmd check'
command, I decided to run it myself and see what
came up. Below is the output. It looks like I am
missing something. Should I ignore it or do something
to correct it?
-Bill
term% disk/kfscmd check
checking file system: main
check free list
lo = 74340; hi = 120722
9537 files
120722 blocks in the file system
65329 used blocks
46138 free blocks
9255 missing blocks
23554 maximum qid path
missing: 67616
missing: 67600
missing: 67585
missing: 67584
missing: 67583
missing: 67582
missing: 67581
missing: 67580
missing: 67579
missing: 67577
missing: 67576
...
term%
next reply other threads:[~2001-02-17 6:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 6:22 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 16:26 William Staniewicz
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=20010217062343.C5162199E6@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).