From: Oleg Drokin <green@namesys.com>
To: Manuel Krause <manuel.krause@mb.tu-ilmenau.de>
Cc: Hans Reiser <reiser@namesys.com>,
reiserfs-list <reiserfs-list@namesys.com>
Subject: Re: Error <-> Partition Correspondance [was Re: Corrupted/unreadable journal: reiser vs. ext3]
Date: Tue, 18 Feb 2003 09:54:14 +0300 [thread overview]
Message-ID: <20030218095414.A16803@namesys.com> (raw)
In-Reply-To: <3E5171BB.20509@mb.tu-ilmenau.de>
Hello!
On Tue, Feb 18, 2003 at 12:35:23AM +0100, Manuel Krause wrote:
> BTW, do the ReiserFS errors nowadays print out a usable partition
> identification (like Chris actual data-logging patches perform at mount,
> e.g.)?
Sometimes it does.
> I mostly always have 2 partitions with ReiserFS mounted, so -- is it
> still meaningless to get an error message related to one of them in my logs?
It depends on what are the messages.
> I posted this circumstance some 3.6-ReiserFS levels ago and someone of
> your team wanted to implement this after his task-list was done, IIRC.
Yes. I have a patch dated back to May 7th, 2002. But it was never
accepted for reason I don't remember already.
I will dig through my email, though. Probably I will give it another try.
Bye,
Oleg
next prev parent reply other threads:[~2003-02-18 6:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 20:05 Corrupted/unreadable journal: reiser vs. ext3 Dirk Schenkewitz
2003-02-13 22:49 ` Zygo Blaxell
2003-02-14 0:32 ` Hans Reiser
2003-02-14 8:18 ` Oleg Drokin
2003-02-14 10:13 ` Andreas Dilger
2003-02-14 10:17 ` Oleg Drokin
2003-02-14 10:50 ` Andreas Dilger
2003-02-14 10:59 ` Oleg Drokin
2003-02-14 13:34 ` Hans Reiser
2003-02-14 16:04 ` Rudy Zijlstra
2003-02-14 19:06 ` Andreas Dilger
2003-02-14 19:19 ` Hans Reiser
2003-02-15 12:51 ` Vitaly Fertman
2003-02-15 13:00 ` Vitaly Fertman
2003-02-18 19:50 ` Hans Reiser
2003-02-18 20:05 ` Vitaly Fertman
2003-02-18 22:18 ` Hans Reiser
2003-02-15 13:04 ` Anders Widman
2003-02-15 13:23 ` Oleg Drokin
2003-02-17 19:43 ` Hans Reiser
2003-02-17 23:35 ` Error <-> Partition Correspondance [was Re: Corrupted/unreadable journal: reiser vs. ext3] Manuel Krause
2003-02-18 6:54 ` Oleg Drokin [this message]
2003-02-21 7:27 ` Manuel Krause
[not found] ` <20030221103757.B28866@namesys.com>
2003-02-21 8:22 ` reiserfs messages cleanup patch Manuel Krause
2003-02-21 8:32 ` Oleg Drokin
2003-02-15 22:37 ` Corrupted/unreadable journal: reiser vs. ext3 Andreas Dilger
2003-02-18 7:04 ` fsck on boot (was: Re: Corrupted/unreadable journal: reiser vs. ext3) Ookhoi
2003-02-18 18:21 ` Corrupted/unreadable journal: reiser vs. ext3 Hans Reiser
2003-02-18 19:22 ` Oleg Drokin
2003-02-18 19:28 ` Hans Reiser
2003-02-18 21:17 ` Valdis.Kletnieks
2003-02-18 22:02 ` Matthias Andree
2003-02-19 6:26 ` Oleg Drokin
2003-02-18 22:23 ` 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=20030218095414.A16803@namesys.com \
--to=green@namesys.com \
--cc=manuel.krause@mb.tu-ilmenau.de \
--cc=reiser@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.