All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Oleg Drokin <green@namesys.com>
Cc: trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client)
Date: Mon, 11 Mar 2002 11:46:54 +0100	[thread overview]
Message-ID: <20020311114654.2901890f.skraw@ithnet.com> (raw)
In-Reply-To: <20020311091458.A24600@namesys.com>
In-Reply-To: <shswuwkujx5.fsf@charged.uio.no> <200203110018.BAA11921@webserver.ithnet.com> <15499.64058.442959.241470@charged.uio.no> <20020311091458.A24600@namesys.com>

On Mon, 11 Mar 2002 09:14:58 +0300
Oleg Drokin <green@namesys.com> wrote:

> Hello!
> 
> On Mon, Mar 11, 2002 at 01:28:42AM +0100, Trond Myklebust wrote:
> >      > this is a weak try of an explanation. All involved fs types are
> >      > reiserfs. The problem occurs reproducably only after (and
> > Which ReiserFS format? Is it version 3.5?
> 
> >    'cat /proc/fs/reiserfs/device/version'
> 
> If this does not work because you have no such file, then look through your
> kernel logs, if you use reiserfs v3.5 on 2.4 kernel, it will show itself
> as such record in the log file: "reiserfs: using 3.5.x disk format"

Hello Oleg, hello Trond, hello Alan,

I have several reiserfs fs in use on this server. boot.msg looks like

<4>reiserfs: checking transaction log (device 08:03) ...
<4>Using r5 hash to sort names
<4>ReiserFS version 3.6.25
<4>VFS: Mounted root (reiserfs filesystem) readonly.
<4>Freeing unused kernel memory: 224k freed
<6>Adding Swap: 265032k swap-space (priority 42)
<4>reiserfs: checking transaction log (device 21:01) ...
<4>Using r5 hash to sort names
<4>ReiserFS version 3.6.25
<4>reiserfs: checking transaction log (device 22:01) ...
<4>Using tea hash to sort names
<4>reiserfs: using 3.5.x disk format
<4>ReiserFS version 3.6.25
<4>reiserfs: checking transaction log (device 08:04) ...
<4>Using r5 hash to sort names
<4>ReiserFS version 3.6.25

I tried to find out which device has which numbers and did a cat /proc/devices:

Block devices:
  2 fd
  8 sd
 11 sr
 22 ide1
 33 ide2
 34 ide3
 65 sd
 66 sd

Interestingly there is no #21. Shouldn't I see a block device 21 here?
More strange the only two existing ide-drives in this system are located on
ide2 and ide3 and should therefore have device numbers 33 and 34, or not?
There is no hd on ide1, only a CDROM (not used during the test). ide0 is
completely empty.
As told earlier this is kernel 2.4.19-pre2.

Enlighten me, please...

Stephan


  reply	other threads:[~2002-03-11 10:47 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-09 12:19 BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client) Stephan von Krawczynski
2002-03-09 19:10 ` Alan Cox
2002-03-10 17:50   ` Stephan von Krawczynski
2002-03-10 22:39 ` Trond Myklebust
2002-03-11  0:18   ` Stephan von Krawczynski
2002-03-11  0:28     ` Trond Myklebust
2002-03-11  6:14       ` Oleg Drokin
2002-03-11 10:46         ` Stephan von Krawczynski [this message]
2002-03-11 10:52           ` Oleg Drokin
2002-03-11 11:00             ` Stephan von Krawczynski
2002-03-11 11:11               ` Oleg Drokin
2002-03-11 11:24                 ` Stephan von Krawczynski
2002-03-11 12:47                 ` Stephan von Krawczynski
2002-03-11 12:59                   ` Oleg Drokin
2002-03-11 14:48                     ` Stephan von Krawczynski
2002-03-11 13:51                       ` Oleg Drokin
2002-03-11 13:59                         ` Trond Myklebust
2002-03-11 14:03                           ` Trond Myklebust
2002-03-11 15:57                           ` Stephan von Krawczynski
2002-03-11 16:31                             ` Hans Reiser
2002-03-15 10:32                             ` Oleg Drokin
2002-03-15 11:02                               ` Stephan von Krawczynski
2002-03-15 11:13                                 ` Oleg Drokin
2002-03-15 11:30                                   ` Stephan von Krawczynski
2002-03-15 11:36                                     ` Sean Neakums
2002-03-15 12:03                                       ` Stephan von Krawczynski
2002-03-15 12:05                                         ` Oleg Drokin
2002-03-15 14:07                                           ` Stephan von Krawczynski
2002-03-21 14:45                                           ` Stephan von Krawczynski
2002-03-21 14:57                                             ` Stephan von Krawczynski
2002-03-21 15:01                                               ` Oleg Drokin
2002-03-21 15:05                                                 ` Stephan von Krawczynski
2002-03-21 15:07                                                   ` Oleg Drokin
2002-03-21 17:15                                                     ` Stephan von Krawczynski
2002-03-22  5:48                                                       ` Oleg Drokin
2002-03-22  0:19                                             ` Trond Myklebust
2002-03-22 11:00                                               ` Stephan von Krawczynski
2002-03-22 11:07                                                 ` Trond Myklebust
2002-03-22 13:19                                                   ` Stephan von Krawczynski
2002-03-15 11:37                                     ` Oleg Drokin
2002-03-18  7:07       ` NIIBE Yutaka
2002-03-18  8:15         ` Trond Myklebust
2002-03-18  9:33           ` NIIBE Yutaka
2002-03-18  9:56             ` Trond Myklebust
2002-03-18 23:57               ` NIIBE Yutaka
2002-03-19 14:45                 ` Trond Myklebust
2002-03-20  0:42                   ` NIIBE Yutaka
2002-03-20  8:30                     ` Trond Myklebust
2002-03-19 15:42               ` Ton Hospel
2002-03-19 18:31                 ` BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and Alan Cox
2002-03-19 22:10                 ` BUG REPORT: kernel nfs between 2.4.19-pre2 (server) and 2.2.21-pre3 (client) Trond Myklebust
2002-03-22 10:33                   ` David Woodhouse
2002-03-22 11:03                     ` Trond Myklebust

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=20020311114654.2901890f.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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.