From: Andreas Franck <afranck@gmx.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, florin@iucha.net (Florin Iucha)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19pre1-ac1
Date: Wed, 27 Feb 2002 23:31:24 +0100 [thread overview]
Message-ID: <02022723312400.01097@dg1kfa> (raw)
Hi Florin, hi Alan,
> With 19-pre1-ac1 on a reiserfs partition I cannot patch a kernel. Patch
> fails with "Invalid cross-device link" or "Out of disk space".
I can reproduce this too on ext2, so this does not seem to be FS related.
However, I do not get this error messages, the patch runs just fine,
but corrupts all files it touches, leaving them to be all a bit less than
1MiB of size, and all exactly the same size.
There is no filesystem corruption however, e2fsck runs just fine without any
error. Just the files are all damaged. I looked inside them, and it seems
huge parts of other files from the patch have been "attached" to them.
> 18-rc2-ac1 works fine on the same partition.
ACK, for me too; as well as 2.4.18-rc2-ac2 for me. The breakage starts with
2.4.18-ac1 here. Plain 2.4.18 from Marcelo works fine as well.
Greetings,
Andreas
next reply other threads:[~2002-02-27 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-27 22:31 Andreas Franck [this message]
2002-02-27 23:41 ` Linux 2.4.19pre1-ac1 Alan Cox
2002-02-28 0:13 ` Andreas Franck
2002-02-28 0:34 ` Alan Cox
2002-02-28 0:27 ` Andreas Franck
2002-02-28 0:32 ` David S. Miller
2002-02-28 1:02 ` Alan Cox
2002-02-28 6:31 ` Florin Iucha
[not found] <fa.kjtklqv.gnqri3@ifi.uio.no>
[not found] ` <fa.g63p78v.1e7kv8e@ifi.uio.no>
2002-02-28 0:19 ` Jonathan Hudson
[not found] <fa.c7mcedv.1a3esq4@ifi.uio.no>
2002-02-27 22:54 ` Jonathan Hudson
2002-02-27 23:48 ` Alan Cox
[not found] ` <fa.g5iqv0v.11magge@ifi.uio.no>
2002-02-27 23:36 ` Jonathan Hudson
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 1:47 Alan Cox
2002-02-27 21:14 ` Florin Iucha
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=02022723312400.01097@dg1kfa \
--to=afranck@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox