From: mjt@nysv.org
To: Henning Westerholt <henning-04@die.informatik.uni-siegen.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Problem with the latest auto snapshot
Date: Mon, 14 Jun 2004 12:21:16 +0300 [thread overview]
Message-ID: <20040614092116.GN4990@nysv.org> (raw)
In-Reply-To: <200406141113.16009.henning-04@die.informatik.uni-siegen.de>
On Mon, Jun 14, 2004 at 11:13:16AM +0200, Henning Westerholt wrote:
>> Could this be because the partition is in use?
>> If it's trafficking data all the time and fsck can't catch up?
>The partition is only temporarily in use, so this should not the case.
I tested this on a 1152-megabyte loopback image, I ran bonnie++ on it
while doing fsck's and I got pretty identical error messages...
>These were the only visible corruption so far. After the mentioned errors, the
>partition now performs stable. I compile several large oss projects without
>problems. Fsck shows also no problems.
>Strange. Perhaps the disk format after the mkfs is "unstable", and it needs
>further use to stabilize it?
I think someone at Namesys, maybe VS or Zam, is better qualified to answer
to this. I'm at a total loss. It doesn't sound reasonable that the file
system must be "driven in" before actual use...
--
mjt
next prev parent reply other threads:[~2004-06-14 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 19:31 Problem with the latest auto snapshot Henning Westerholt
2004-06-12 19:46 ` mjt
2004-06-13 13:37 ` Henning Westerholt
2004-06-13 13:43 ` mjt
2004-06-14 9:13 ` Henning Westerholt
2004-06-14 9:21 ` mjt [this message]
2004-06-14 18:08 ` Hans Reiser
2004-06-15 8:06 ` Alex Zarochentsev
2004-06-15 8:14 ` Alex Zarochentsev
2004-06-15 16:50 ` Henning Westerholt
2004-06-15 17:44 ` Alex Zarochentsev
2004-06-15 18:19 ` Henning Westerholt
2004-06-14 18:22 ` Alex Zarochentsev
2004-06-14 22:55 ` Henning Westerholt
2004-06-15 4:34 ` Alex Zarochentsev
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=20040614092116.GN4990@nysv.org \
--to=mjt@nysv.org \
--cc=henning-04@die.informatik.uni-siegen.de \
--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.