All of lore.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <reiserfs@nn7.de>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: trouble with reiserfs on ppc vs-3050: wait_buffer_until_released ...
Date: 25 Apr 2003 12:12:55 +0200	[thread overview]
Message-ID: <1051265575.1656.37.camel@localhost> (raw)
In-Reply-To: <20030425094630.GH10802@namesys.com>

On Fri, 2003-04-25 at 11:46, Oleg Drokin wrote:

> Well, fsck is expected to fix things.

actually I don't know why a wait_buffer_until_released (waiting forever)
can happen...

> The strange thing is how you get into error state.
> 
> > IIRC there was no unclean reboot before that vs-3050 thing appeared.
> 
> 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.

(The 3.6.6 tools are compiled but not installed) 

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.

if a wrong partition table can cause that then good+ shame on me... if
not well then its bad.

> > Or could this be caused by "repartitioning but not reboot and then
> > mkreiserfs" ? I did not reboot as the last partition was hfs+ and all I
> > did was deleting+creating a linux partition instead...
> 
> Well, if fdisk told you to reboot and you did not, this is bad,
> but it may not cause such things.

well it definitely did, but as I said I recreated a partition of same
size... maybe it is all different with apple partition tables. next time
.
> > Can one check whether partition sizes are the same as reiserfs thinks ?
> 
> Sure. reiserfsck does this. (it checks that fs is less or equal than underlying block device)
> 
> > Count of blocks on the device: 5476231
> (20.89016342163085937500 G)
> 
> > /dev/hda7         Apple_UNIX_SVR2 home                43809856 @ 73400384  ( 20.9G)  Linux native
> 
> This looks close enough, but is subject to rounding errors ;)

:-))

S.


  reply	other threads:[~2003-04-25 10:12 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 [this message]
2003-04-25 10:28               ` Oleg Drokin
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=1051265575.1656.37.camel@localhost \
    --to=reiserfs@nn7.de \
    --cc=green@namesys.com \
    --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.