All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Willi W." <willi.w@gmx.at>
To: reiserfs-list@namesys.com
Subject: Re: Application Problems with Reiser4/19.01.2004-fixed (truncated)
Date: Mon, 26 Jan 2004 16:46:01 +0100	[thread overview]
Message-ID: <40153639.6080609@gmx.at> (raw)
In-Reply-To: <16401.3844.21706.388236@laputa.namesys.com>

Hi!

>Hmm... can you run overnet under strace (up to the failure) and send the
>output to me?

--

all files in the ./temp directory should be reloaded at startup.

access to the directory in the strace output:

--

      --
      [pid 21379] <... write resumed> )       = 1
      [pid 21381] stat64("/mnt/reiser4/overtest/temp",  <unfinished ...>
      [pid 21379] write(0, "n", 1n <unfinished ...>
      [pid 21381] <... stat64 resumed> {st_mode=S_IFDIR|S_ISVTX|0755,
      st_size=3, ...}) = 0
      [pid 21379] <... write resumed> )       = 1
      [pid 21381] open("/mnt/reiser4/overtest/share.dat", O_RDONLY
      <unfinished ...>
      [pid 21379] write(0, "e", 1e <unfinished ...>
      [pid 21381] <... open resumed> )        = 6
      [pid 21379] <... write resumed> )       = 1
      [pid 21381] lseek(6, 0, SEEK_CUR <unfinished ...>
      [pid 21379] write(0, "t", 1t <unfinished ...>
      [pid 21381] <... lseek resumed> )       = 0

--

i cannot tell if this is correct (stat64...=0)


the whole strace is attached. (sent to nikita)

after the test, the filesystem was _corrupt again_ (wasnt before) - fscp
output attached (also sent to nikita)

      ...
      Error: Node (23), item (4): StatData of the file
      [100de:636f6e74616374:100f1] has the wrong bytes (96966), Should be
      (11504).
      Plugin (stat40).
      Error: Node (23), item (5): StatData of the file
      [100de:667269656e642e:100f3] has the wrong bytes (55), Should be
      (5). Plugin
      (stat40).
      ...

--

p.s. i have harddrive writecache turned on - is this good/bad/should'nt
matter ? (again - no problems under reiser3)

hdparm /dev/hdb

/dev/hdb:
   multcount    = 16 (on)
   IO_support   =  1 (32-bit)
   unmaskirq    =  1 (on)
   using_dma    =  1 (on)
   readahead    = 256 (on)
   geometry     = 39770/16/63, sectors = 40088160, start = 0
   AdvancedPM=no WriteCache=enabled

regards
Willi



      reply	other threads:[~2004-01-26 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 19:16 Application Problems with Reiser4/19.01.2004-fixed Willi W.
2004-01-23 11:04 ` Nikita Danilov
2004-01-23 11:35   ` Willi W.
2004-01-23 12:09     ` Nikita Danilov
2004-01-26 15:46       ` Willi W. [this message]

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=40153639.6080609@gmx.at \
    --to=willi.w@gmx.at \
    --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.