From: Oleg Drokin <green@namesys.com>
To: Francois-Rene Rideau <fare@tunes.org>
Cc: reiserfs-list@namesys.com
Subject: Re: mkreiserfs -s 1024 makes unmountable partitions
Date: Mon, 27 Jan 2003 14:33:05 +0300 [thread overview]
Message-ID: <20030127143305.A26767@namesys.com> (raw)
In-Reply-To: <20030127112651.GA10556@hell.mine.nu>
Hello!
On Mon, Jan 27, 2003 at 12:26:51PM +0100, Francois-Rene Rideau wrote:
> > ftp://ftp.suse.com/pub/people/mason/patches/data-logging
> Thanks for the tip. Can you tell me which patches are needed?
01-relocation-5.diff.gz is the one.
> >> In any case, I think that it is a bug that mkreiserfs doesn't check
> >> the consistency of its parameters with what the kernel is able to handle.
> > No, that's not a bug. mkreiserfs cannot know if you are just making
> > a filesystem and planning to reboot into proper kernel later
> > (or even move the disk to other system).
> > Also it cannot detect if your current kernel have any patches applied or not.
> Well, it could detect that the kernel version is under some version, issue
> a Warning that a patch is required wrt vanilla kernel of same version, and
Well. But given the trend that lots of users are using distro kernels only,
and e.g. SuSE ships these patches for some time already, such a warning
will cause lots of confusion.
> give a pointer to said patch -- that would completely solve the issue with
> newbies like me asking you this question.
So far we have not found any good way to print warning only when it is really needed.
Always printing the warning is not very good idea in my opinion.
Bye,
Oleg
next prev parent reply other threads:[~2003-01-27 11:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 22:15 recovery of crashed reiserfs disk? Francois-Rene Rideau
2003-01-18 7:09 ` Ookhoi
2003-01-18 8:51 ` Oleg Drokin
2003-01-18 9:01 ` Ookhoi
2003-01-18 11:57 ` Francois-Rene Rideau
2003-01-20 14:20 ` Francois-Rene Rideau
2003-01-21 21:33 ` Crash again! Francois-Rene Rideau
2003-01-22 5:57 ` Ookhoi
2003-01-22 10:03 ` Francois-Rene Rideau
2003-01-24 22:28 ` Crash: the problem was DMA! Francois-Rene Rideau
2003-01-25 16:15 ` Manuel Krause
2003-01-26 18:18 ` mkreiserfs -s 1024 makes unmountable partitions Francois-Rene Rideau
2003-01-27 4:49 ` Ookhoi
2003-01-27 5:23 ` Brian Tinsley
2003-01-27 6:59 ` Oleg Drokin
2003-01-27 7:20 ` Scott R. Every
2003-01-27 7:25 ` Oleg Drokin
2003-01-27 7:37 ` Scott R. Every
2003-01-27 7:42 ` Oleg Drokin
2003-01-29 11:37 ` Hans Reiser
2003-01-27 11:26 ` Francois-Rene Rideau
2003-01-27 11:33 ` Oleg Drokin [this message]
2003-01-27 11:42 ` Francois-Rene Rideau
2003-01-27 12:46 ` Francois-Rene Rideau
2003-01-27 14:20 ` Manuel Krause
2003-01-28 2:41 ` Oh no! Not again! Francois-Rene Rideau
2003-01-28 11:00 ` Vitaly Fertman
2003-01-29 19:31 ` Francois-Rene Rideau
2003-01-29 20:17 ` Vitaly Fertman
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=20030127143305.A26767@namesys.com \
--to=green@namesys.com \
--cc=fare@tunes.org \
--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.