From: Alex Zarochentsev <zam@namesys.com>
To: f00bar <f00bar@sbcglobal.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Something is not right...
Date: Tue, 17 Aug 2004 00:29:23 +0400 [thread overview]
Message-ID: <20040816202922.GJ4703@backtop.namesys.com> (raw)
In-Reply-To: <20040815220002.65404.qmail@web80806.mail.yahoo.com>
Hello
On Sun, Aug 15, 2004 at 03:00:02PM -0700, f00bar wrote:
> I am having an issue creating and mounting a new
> partition with 2.6.8-rc4-mm1 & and latest snapshot.
>
> # mkfs.reiser4 -qf /dev/sdc1
> # mount -treiser4 /dev/sdc1 /var/tmp/portage
>
> if I try:
> # ls /var/tmp/portage
> ls: reading directory /var/tmp/portage: Input/output
> error
what reiser4 messages are in the syslog?
>
> so... here is some more info...
>
> I have 8K stacks and all debugging options for resier4
> enabled.
>
> # uname -a
> 2.6.8-rc4-mm1 #1 SMP Sun Aug 15 14:08:05 CDT 2004 i686
> AMD Athlon(tm) MP 2400+ AuthenticAMD GNU/Linux
>
> # debugfs.reiser4 /dev/sdc1
> debugfs.reiser4 1.0.0
> Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser,
> licensing governed by reiser4progs/COPYING.
>
> Master super block (16):
> magic: ReIsEr4
> blksize: 4096
> format: 0x0 (format40)
> uuid: 92934d00-0000-0000-0000-000000000000
> label: <none>
>
> Format super block (17):
> plugin: format40
> description: Disk-format for reiser4, ver. 1.0.0
> magic: ReIsEr40FoRmAt
> flushes: 0
> mkfs id: 0x273042db
> blocks: 1110485
> free blocks: 1110419
> root block: 23
> tail policy: 0x2 (smart)
> next oid: 0x10000
> file count: 0
> tree height: 2
> key policy: LARGE
>
> FS status block (21):
> FS marked consistent
>
>
> # debugfs.reiser4 -t /dev/sdc1
> debugfs.reiser4 1.0.0
> Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser,
> licensing governed by reiser4progs/COPYING.
>
> NODE (23) LEVEL=2 ITEMS=1 SPACE=4022 MKFS
> ID=0x273042db FLUSH=0x0
> #0 NPTR (nodeptr40): [29:1(SD):0:2a:0] OFF=28, LEN=8,
> flags=0x0 UNITS=1
> [24]
> ==============================================================================
> NODE (24) LEVEL=1 ITEMS=2 SPACE=3808 MKFS
> ID=0x273042db FLUSH=0x0
> #0 SD (stat40): [29:1(SD):0:2a:0] OFF=28, LEN=82,
> flags=0x0 UNITS=1
> exts: 3
> mask: 0x13
> plugin: sdext_lw
> offset: 2
> len: 14
> mode: drwxr-xr-x
> nlink: 3
> size: 2
> plugin: sdext_unix
> offset: 16
> len: 28
> uid: 0
> gid: 0
> atime: Sun Aug 15 16:43:34 2004
> mtime: Sun Aug 15 16:43:34 2004
> ctime: Sun Aug 15 16:43:34 2004
> rdev: 100
> bytes: 100
> plugin: sdext_plug
> offset: 44
> len: 38
> Pset count: 9
> permission : id = 0
> formatting : id = 2 (smart)
> hash : id = 1 (r5_hash)
> fibration : id = 2 (ext_1_fibre)
> statdata : id = 0 (stat40)
> diritem : id = 2 (cde40)
> crypto : id = 0
> digest : id = 0
> compress : id = 0
> ------------------------------------------------------------------------------
> #1 DIRITEM (cde40): [2a:0(NAME):0:0:0] OFF=110,
> LEN=102, flags=0x0 UNITS=2
> NR NAME OFFSET HASH
> SDKEY
> 0 . 54
> 0000000000000000:0000000000000000 0000291:000002a
> 1 .. 78
> 0000000000000000:0000000000000000 0000291:000002a
> ==============================================================================
>
--
Alex.
next prev parent reply other threads:[~2004-08-16 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 22:00 Something is not right f00bar
2004-08-16 20:29 ` Alex Zarochentsev [this message]
2004-08-17 4:45 ` f00bar
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=20040816202922.GJ4703@backtop.namesys.com \
--to=zam@namesys.com \
--cc=f00bar@sbcglobal.net \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.