All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Saveliev <vs@namesys.com>
To: Andrew Snare <asnare@allshare.nl>
Cc: Paul Wagland <PWagland@allshare.nl>, reiserfs-list@namesys.com
Subject: Re: Block corruption
Date: Tue, 08 Jun 2004 19:55:45 +0400	[thread overview]
Message-ID: <1086710145.1830.106.camel@tribesman.namesys.com> (raw)
In-Reply-To: <s0c5e9fc.070@allshare.nl>

Hello

On Tue, 2004-06-08 at 18:31, Andrew Snare wrote:
> Vladimir Saveliev suggested:
> > Well, reiserfs needs to include device name into its warnings
> > Until it is not done you might want to do
> > 
> > find /mountpoint -inum 52653 
> > for each of your reiserfs filesystem.
> 
> That number comes from the vs-13070 messages. They're of the form:
> > vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to
> > find stat data of [52570 52653 0x0 SD]
> 
> What are these numbers near the end? You've referred to the second as
> the inode, but we'd like to understand more clearly what's going on.
> 
reiserfs builds files of items. Item is stored in an ondisk tree. Each
file has at least one item - stat data item. Each item has key. Key has
4 components.
[52570 52653 0x0 SD] is key of stat data. Key of stat data was taken
from directory entry.
First key component is unique identifier of directory in which file was
created.
Second key component is unique identifier of file itself. This is what
is reported in st_ino field of struct stat
Third key component is offset within a file. It is 0 for items if stat
data type.
Fourth key component is item type.


> Cheers,
> 
>  - Andrew
> 


  reply	other threads:[~2004-06-08 15:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-08 14:31 Block corruption Andrew Snare
2004-06-08 15:55 ` Vladimir Saveliev [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-31 18:19 block corruption Rann Bar-On
2019-08-31 20:26 ` Rann Bar-On
2019-08-31 23:04   ` Chris Murphy
2019-08-31 23:39     ` Rann Bar-On
2019-08-31 23:48       ` Qu Wenruo
2019-09-01 17:39         ` Rann Bar-On
2019-09-01 20:09           ` Chris Murphy
2019-09-01 20:35             ` Rann Bar-On
2019-09-02  5:33               ` Qu Wenruo
2019-09-02  6:27                 ` Qu Wenruo
2004-06-08 13:36 Block corruption Andrew Snare
2004-06-08 14:12 ` Vladimir Saveliev

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=1086710145.1830.106.camel@tribesman.namesys.com \
    --to=vs@namesys.com \
    --cc=PWagland@allshare.nl \
    --cc=asnare@allshare.nl \
    --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.