Hi
[EMAIL PROTECTED] wrote:
Hi...
I had an Oops under kernel 2.4.9, I believe it is from reiserfs.
I was doing ./configure under kdelibs-2.1.1 trying to make and install it
when this occured. the kdelibs directory is located in a reiserfs partition.
When the oops happens, I can't
On Mon, 24 Sep 2001 20:41:03 +0400
Vladimir V. Saveliev [EMAIL PROTECTED] wrote:
If you ./configure again - does it oops?
If yes - can you please ksymoops(8) the dump?
it does oops, and in the same place, everytime.
where is the dump?
could it be from bad blocks in the hard disk, it is an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 21 Sep 2001, Gregory Ade wrote:
As it is, compiling with a cleaner configuration (minus the cruft) was
successful.
Hmm... but now I'm running into this same problem again.
The way our backup program works, it allows you to run a script
[EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2001 20:41:03 +0400
Vladimir V. Saveliev [EMAIL PROTECTED] wrote:
If you ./configure again - does it oops?
If yes - can you please ksymoops(8) the dump?
it does oops, and in the same place, everytime.
where is the dump?
Do you see something
On Mon, 24 Sep 2001 [EMAIL PROTECTED] wrote:
If you ./configure again - does it oops?
If yes - can you please ksymoops(8) the dump?
it does oops, and in the same place, everytime.
where is the dump?
Immediately after the oops (if your system is usable), you could do:
dmesg|ksymoops
On Mon, 24 Sep 2001 19:40:09 +0200 (CEST)
Rasmus Bøg Hansen [EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2001 [EMAIL PROTECTED] wrote:
If you ./configure again - does it oops?
If yes - can you please ksymoops(8) the dump?
it does oops, and in the same place, everytime.
where is the
It stops with check_objectid_map: map corrupted.
Anybody interested in the core dump?
What other information can I provide?
-Winfried
On Monday, September 24, 2001 14:46:09 PM -0400 Chris Mason wrote:
On Monday, September 24, 2001 10:09:59 PM +0800 Beau Kuiper
[EMAIL PROTECTED] wrote:
Hi all again,
I have updated my last set of patches for reiserfs to run on the 2.4.10
kernel.
The new set of patches create a
Sorry, that I've cross posted but this is one of the worst cases...
First my system spec:
Athlon II 1 GHz (0.18µm)
MSI MS-6167 Rev 1.0B (AMD Irongate C4, without bypass)
640 MB PC100-2-2-2 SDRAM
AHA-2940UW (40 MB/sec) I know it could be to slow, but it should be compatible
IBM DDYS-T18350N
IBM
All spin-downs occur during heavy dbench (16/32/+ clients) on the same
partition (/dev/sda8; the last one).
Most likely the drive is overheating and is spinning down/up again to
recalibrate itself. you should give it a better cooling ;-)
Dirk
On Mon, 24 Sep 2001 21:37:41 +0400
Vladimir V. Saveliev [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
On Mon, 24 Sep 2001 20:41:03 +0400
Vladimir V. Saveliev [EMAIL PROTECTED] wrote:
If you ./configure again - does it oops?
If yes - can you please ksymoops(8) the dump?
it
Hi all again,
I have updated my last set of patches for reiserfs to run on the 2.4.10
kernel.
The new set of patches create a new method to do kupdated syncs. On
filesystems that do no support this new method, the regular write_super
method is used. Then reiserfs on kupdated super_sync,
On Monday, September 24, 2001 10:09:59 PM +0800 Beau Kuiper
[EMAIL PROTECTED] wrote:
Hi all again,
I have updated my last set of patches for reiserfs to run on the 2.4.10
kernel.
The new set of patches create a new method to do kupdated syncs. On
filesystems that do no support this
Thanks to everyone who has helped me so far, and I look forward to further
comments and assistance,
Beau Kuiper
[EMAIL PROTECTED]
And I should attach the patch :-) Sorry about that
Beau Kuiper
[EMAIL PROTECTED]
--- v2.4.10/linux/fs/buffer.c Mon Sep 24 14:04:05 2001
+++ linux/fs/buffer.c
On Mon, Sep 24, 2001 at 09:15:19AM -0700, Nicholas Knight [EMAIL PROTECTED] wrote:
[turning off write-cache]
I'm sorry, but that's not acceptable.
(I had it turned off for a long time, until I reasoned: real power-outages
are very rare, so I can leave it turned on anyways and risk a
On Mon, 24 Sep 2001, Alan Cox wrote:
Those drives should be blacklisted and rejected as soon as someone tries
to mount those pieces rw. Either the drive can make guarantees when a
write to permanent storage has COMPLETED (either by switching off the
cache or by a flush operation) or it
On Mon, Sep 24, 2001 at 06:53:03PM +0200, Matthias Andree
[EMAIL PROTECTED] wrote:
Linear writing as dd mostly does is BTW something which should never be
affected by write caches.
A write cache can and will speed up linear writes on typical ide setups.
--
-==-
On Monday 24 September 2001 09:53 am, Matthias Andree wrote:
On Mon, 24 Sep 2001, Nicholas Knight wrote:
Turn it off (I have no idea of internals, but I presume it'll
still be a write-through cache, so reading back will still be
served from the buffer). Do hdparm -W0 /dev/hd[a-h].
18 matches
Mail list logo