From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: [9fans] kfs error
Date: Fri, 28 Sep 2001 22:27:16 -0400 [thread overview]
Message-ID: <20010929022719.8A2A819A8A@mail.cse.psu.edu> (raw)
i'm trying to copy a ~120MB CD image from a system i'm
cpu'd into back to my terminal. the cp fails, complaining
"file system full". on the terminal console is printed the
message "dnodebuf: trip indirect". kfscmd check tells me
i've got 760780 free blocks (1K blocks), which matches
what i think i should have.
i did a kfscmd check rft, and it found one file with a bad
xtag, but that was it. any idea what's going on? i've found
the message in kfs (disk/kfs/dentry.c:89), but i'm not
exactly clear on what it's doing there. can anyone save me
the trouble of figuring out what's wrong with my fils
system? any help, much appreciated.
-α.
next reply other threads:[~2001-09-29 2:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-29 2:27 anothy [this message]
2001-09-29 2:52 ` Boyd Roberts
2001-09-29 2:57 jmk
2001-09-29 10:14 forsyth
2001-09-29 12:41 presotto
2001-09-29 12:57 ` Boyd Roberts
2001-10-01 9:56 ` Wladimir Mutel
2001-10-01 10:45 ` Boyd Roberts
2001-10-01 14:10 ` Wladimir Mutel
2001-09-30 3:51 anothy
2001-09-30 5:07 jmk
2001-10-01 12:26 rob pike
2001-10-01 13:25 ` William Josephson
2002-01-29 16:25 anothy
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=20010929022719.8A2A819A8A@mail.cse.psu.edu \
--to=anothy@cosym.net \
--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).