From: Oleg Drokin <green@namesys.com>
To: Soeren Sonnenburg <reiserfs@nn7.de>
Cc: reiserfs-list@namesys.com
Subject: Re: trouble with reiserfs on ppc vs-3050: wait_buffer_until_released ...
Date: Fri, 25 Apr 2003 14:28:12 +0400 [thread overview]
Message-ID: <20030425102812.GA24352@namesys.com> (raw)
In-Reply-To: <1051265575.1656.37.camel@localhost>
Hello!
On Fri, Apr 25, 2003 at 12:12:55PM +0200, Soeren Sonnenburg wrote:
> > Well, fsck is expected to fix things.
> actually I don't know why a wait_buffer_until_released (waiting forever)
> can happen...
Well, we know why the wait_buffer_until_released problem,
because of bitmap corruption. (block that is used was marked free and was allocated for
new data).
> > Hm. But do you run reiserfsck on boot?
> Honestly I don't know... if debian does then yes...
> Hmmhh, from the scripts in /etc/rcS.d to tell it checks the rootfs and
> later on calls fsck for each filesystem. If fsck calls reiserfsck then
> the version in debian unstable, i.e. 3.6.4-5 was used to check the fs.
Well, ok, 3.6.4-5 does not doo anything on boot yet. Hm.
> So how did I get there... all I did was:
> 1) partition the disk
> 2) mkreiserfs (without reboot)
> 3) copy the stuff over
> 4) reboot
> 5) boot into single user copy the rest from /home over
> 6) mount partition on /home
> no crash inbetween that.
Hm.
Ok, is this a new box? any chance to check if the memory is right?
Bye,
Oleg
next prev parent reply other threads:[~2003-04-25 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 8:11 trouble with reiserfs on ppc vs-3050: wait_buffer_until_released Soeren Sonnenburg
2003-04-25 8:35 ` Soeren Sonnenburg
2003-04-25 8:47 ` Oleg Drokin
2003-04-25 9:05 ` Soeren Sonnenburg
2003-04-25 9:19 ` Oleg Drokin
2003-04-25 9:33 ` Soeren Sonnenburg
2003-04-25 9:46 ` Oleg Drokin
2003-04-25 10:12 ` Soeren Sonnenburg
2003-04-25 10:28 ` Oleg Drokin [this message]
2003-04-26 22:46 ` Soeren Sonnenburg
2003-04-28 5:18 ` Oleg Drokin
2003-04-28 19:54 ` Soeren Sonnenburg
2003-04-29 5:21 ` Oleg Drokin
2003-04-25 8:41 ` Vitaly Fertman
2003-04-25 9:01 ` Soeren Sonnenburg
2003-04-26 15:27 ` none
2003-04-28 20:14 ` Hans Reiser
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=20030425102812.GA24352@namesys.com \
--to=green@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=reiserfs@nn7.de \
/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.