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 11:05:56 +0200 [thread overview]
Message-ID: <1051261556.3513.31.camel@localhost> (raw)
In-Reply-To: <20030425084742.GA22827@namesys.com>
On Fri, 2003-04-25 at 10:47, Oleg Drokin wrote:
> Hello!
>
> On Fri, Apr 25, 2003 at 10:35:23AM +0200, Soeren Sonnenburg wrote:
>
> > The filesystem was freshly created (today) and 10G were tarred on the
> > disk...
> > the /home partition is reiserfs (where that file is on), / is ext3
> > As I was using reiserfs for a quite long time on any kind of i386
> > hardware I guess it is a little/big endian issue.
>
> There are no known endianness issues in reiserfs code now.
> You di not had reboot or something like that after you copied the data over?
I rebooted ... it is the /home partition.
> What is the latest reiserfsck reports for your fs?
the 3.6.6 version did find some corruption in superblock (one bit ?!)
which could be fixed with fix-fixable
I will try to acces that file but first send this mail (as it is send
from that particular machine)
Soeren.
next prev parent reply other threads:[~2003-04-25 9:05 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 [this message]
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
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=1051261556.3513.31.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.