From: "E.Gryaznova" <grev@namesys.com>
To: f00bar <f00bar@sbcglobal.net>
Cc: Alex Zarochentsev <zam@namesys.com>, reiserfs-list@namesys.com
Subject: Re: I/O Errors
Date: Tue, 28 Sep 2004 19:02:01 +0400 [thread overview]
Message-ID: <41597CE9.9020401@namesys.com> (raw)
In-Reply-To: <20040928002645.19446.qmail@web80810.mail.yahoo.com>
Hello.
Would you please send us the #pvscan, #pvdisplay, #vgdislpay,
#lvdisplay and #lvs --version outputs.
Thanks,
Lena.
f00bar wrote:
>Hi Alex,
>
>Thanks for your assistance.
>
>When I mount the partition, (actually a logical
>volume) the following is written to syslog.
>
>Sep 27 19:17:32 yin-yang ef_hash_table: 8192 buckets
>Sep 27 19:17:32 yin-yang z_hash_table: 8192 buckets
>Sep 27 19:17:32 yin-yang z_hash_table: 8192 buckets
>Sep 27 19:17:32 yin-yang j_hash_table: 16384 buckets
>Sep 27 19:17:32 yin-yang loading reiser4
>bitmap......done (148 jiffies)
>Sep 27 19:17:32 yin-yang d_cursor_hash_table: 256
>buckets
>
>
>I perform an "ls" the following is written to the
>console (I assume stderr) but nothing is written to
>syslog.
>
>ls: reading directory /var/tmp/portage: Input/output
>error
>total 0
>
>
>
>The following is the output from fsck:
>
>yin-yang log # fsck.reiser4 /dev/vgsdc1/reiser4
>*******************************************************************
>This is an EXPERIMENTAL version of fsck.reiser4. Read
>README first.
>*******************************************************************
>
>Fscking the /dev/vgsdc1/reiser4 block device.
>Will check the consistency of the Reiser4 SuperBlock.
>Will check the consistency of the Reiser4 FileSystem.
>Continue?
>(Yes/No): yes
>***** fsck.reiser4 started at Mon Sep 27 19:23:14 2004
>Reiser4 journal (journal40) on /dev/vgsdc1/reiser4: 0
>transactions replayed of the total 0 blocks.
>Reiser4 fs was detected on /dev/vgsdc1/reiser4.
>Master super block (16):
>magic: ReIsEr4
>blksize: 4096
>format: 0x0 (format40)
>uuid: 3581757c-9576-4ed6-ba21-59863d2950b1
>label: <none>
>
>Format super block (17):
>plugin: format40
>description: Disk-format for reiser4, ver.
>1.0.2-pre1
>magic: ReIsEr40FoRmAt
>flushes: 0
>mkfs id: 0x4e9bfc27
>blocks: 553984
>free blocks: 553937
>root block: 23
>tail policy: 0x2 (smart)
>next oid: 0x10000
>file count: 0
>tree height: 2
>key policy: LARGE
>
>
>CHECKING STORAGE TREE
> Read nodes 2
> Nodes left in the tree 2
> Leaves of them 1, Twigs of them 1
> Time interval: Mon Sep 27 19:23:14 2004 - Mon
>Sep 27 19:23:14 2004
>CHECKING EXTENT REGIONS.
> Read twigs 1
> Time interval: Mon Sep 27 19:23:14 2004 - Mon
>Sep 27 19:23:14 2004
>CHECKING SEMANTIC TREE
> Found 1 objects.
> Time interval: Mon Sep 27 19:23:14 2004 - Mon
>Sep 27 19:23:14 2004
>***** fsck.reiser4 finished at Mon Sep 27 19:23:14
>2004
>Closing fs...done
>
>FS is consistent.
>
>Regards,
>John Baxter
>
>
>
>
>
next prev parent reply other threads:[~2004-09-28 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 0:38 I/O Errors f00bar
2004-09-27 15:53 ` Alex Zarochentsev
2004-09-28 0:26 ` f00bar
2004-09-28 15:02 ` E.Gryaznova [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 9:42 i/o errors Bernd Schubert
2004-06-23 14:00 ` Fabien Salvi
2004-06-23 15:08 ` Bernd Schubert
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=41597CE9.9020401@namesys.com \
--to=grev@namesys.com \
--cc=f00bar@sbcglobal.net \
--cc=reiserfs-list@namesys.com \
--cc=zam@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.