Re: Error messages while moving files to reiser4 fs
Le 22.04.2005 10:43, Vladimir Saveliev a écrit : Hello On Fri, 2005-04-22 at 10:48, Damien Wyart wrote: Hello, While moving some iso images from a jfs partition to a reiser4 one (very recently created with latest reiser4progs), I got a bunch of errors looking like these : Apr 22 07:31:48 brouette kernel: [ext3_write_inode+69/81] ext3_write_inode+0x45/0x51 Apr 22 07:31:48 brouette kernel: [pg0+955208632/1069118464] extent_balance_dirty_pages+0x94/0xd4 [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955209911/1069118464] extent_write_flow+0x4bf/0x6dc [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955199673/1069118464] nr_units_extent+0xf/0x1a [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955210889/1069118464] write_extent+0x0/0x4f [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955274160/1069118464] append_and_or_overwrite+0x198/0x39e [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955274821/1069118464] write_flow+0x8f/0x95 [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955275498/1069118464] write_file+0x96/0xc0 [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955276110/1069118464] write_unix_file+0x23a/0x48c [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955095464/1069118464] reiser4_write+0x8f/0xff [reiser4] Apr 22 07:31:48 brouette kernel: [vfs_write+236/339] vfs_write+0xec/0x153 Apr 22 07:31:48 brouette kernel: [sys_write+81/128] sys_write+0x51/0x80 Apr 22 07:31:48 brouette kernel: [sysenter_past_esp+82/117] sysenter_past_esp+0x52/0x75 Apr 22 07:31:48 brouette kernel: [ext3_write_inode+69/81] ext3_write_inode+0x45/0x51 [snip] Where do those ext3_write_inode come from ? Aren't they strange ? I do not know at all what they mean... I stupidly reformatted the partition without doing a fsck :( so I can't provide much more information, I'm afraid. Can you reproduce this problem? did you do: cp /tmp_jfs/* /tmp_reiser4/? What I do not get is why some messages appear to be related to ext3. reiser4 calls balance_dirty_pages()-writeback_inodes() which deals with inodes of other mounted filesystems. My root fs is ext3-formatted ; here are my df output : /dev/sdb2 ext31.4G 456M 874M 35% / /dev/sdb5 reiserfs3.5G 3.2G 291M 92% /usr /dev/sdb6 reiserfs 15G 6.1G 8.6G 42% /home /dev/sdb7 reiserfs4.9G 33M 4.9G 1% /tmp /dev/sdb8 jfs9.8G 7.7G 2.2G 79% /tmp_jfs /dev/sdb9 xfs9.8G 6.6G 3.2G 68% /tmp_xfs /dev/sdb11 reiser43.4G 236K 3.4G 1% /tmp_reiser4 The system is vanilla 2.6.11.7 with reiser4 patch from ftp.namesys.com. ~~ laurent signature.asc Description: OpenPGP digital signature
Re: Error messages while moving files to reiser4 fs
Hello On Fri, 2005-04-22 at 14:16, Laurent Riffard wrote: Le 22.04.2005 10:43, Vladimir Saveliev a écrit : Hello On Fri, 2005-04-22 at 10:48, Damien Wyart wrote: Hello, While moving some iso images from a jfs partition to a reiser4 one (very recently created with latest reiser4progs), I got a bunch of errors looking like these : Apr 22 07:31:48 brouette kernel: [ext3_write_inode+69/81] ext3_write_inode+0x45/0x51 Apr 22 07:31:48 brouette kernel: [pg0+955208632/1069118464] extent_balance_dirty_pages+0x94/0xd4 [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955209911/1069118464] extent_write_flow+0x4bf/0x6dc [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955199673/1069118464] nr_units_extent+0xf/0x1a [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955210889/1069118464] write_extent+0x0/0x4f [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955274160/1069118464] append_and_or_overwrite+0x198/0x39e [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955274821/1069118464] write_flow+0x8f/0x95 [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955275498/1069118464] write_file+0x96/0xc0 [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955276110/1069118464] write_unix_file+0x23a/0x48c [reiser4] Apr 22 07:31:48 brouette kernel: [pg0+955095464/1069118464] reiser4_write+0x8f/0xff [reiser4] Apr 22 07:31:48 brouette kernel: [vfs_write+236/339] vfs_write+0xec/0x153 Apr 22 07:31:48 brouette kernel: [sys_write+81/128] sys_write+0x51/0x80 Apr 22 07:31:48 brouette kernel: [sysenter_past_esp+82/117] sysenter_past_esp+0x52/0x75 Apr 22 07:31:48 brouette kernel: [ext3_write_inode+69/81] ext3_write_inode+0x45/0x51 [snip] Where do those ext3_write_inode come from ? Aren't they strange ? No. That stack trace does not have to be precisely correct. I guess that routine which prints it merely tries to convert binary data it finds on a stack to function names and offsets within those functions. On the other hand, there could be something like: extent_balance_dirty_pages-balance_dirty_pages-writeback_inodes-sync_sb_inodes-generic_sync_sb_inodes- __writeback_single_inode-__sync_single_inode-write_inode-ext3_write_inode I do not know at all what they mean... I stupidly reformatted the partition without doing a fsck :( so I can't provide much more information, I'm afraid. Can you reproduce this problem? did you do: cp /tmp_jfs/* /tmp_reiser4/? What I do not get is why some messages appear to be related to ext3. reiser4 calls balance_dirty_pages()-writeback_inodes() which deals with inodes of other mounted filesystems. My root fs is ext3-formatted ; here are my df output : /dev/sdb2 ext31.4G 456M 874M 35% / /dev/sdb5 reiserfs3.5G 3.2G 291M 92% /usr /dev/sdb6 reiserfs 15G 6.1G 8.6G 42% /home /dev/sdb7 reiserfs4.9G 33M 4.9G 1% /tmp /dev/sdb8 jfs9.8G 7.7G 2.2G 79% /tmp_jfs /dev/sdb9 xfs9.8G 6.6G 3.2G 68% /tmp_xfs /dev/sdb11 reiser43.4G 236K 3.4G 1% /tmp_reiser4 The system is vanilla 2.6.11.7 with reiser4 patch from ftp.namesys.com. ~~ laurent
Re: Error messages while moving files to reiser4 fs
While moving some iso images from a jfs partition to a reiser4 one (very recently created with latest reiser4progs), I got a bunch of errors looking like these : [...] I do not know at all what they mean... I stupidly reformatted the partition without doing a fsck :( so I can't provide much more information, I'm afraid. * Vladimir Saveliev [EMAIL PROTECTED] [050422 10:43]: Can you reproduce this problem? Unfortunately, no. Tried to copy the same isos again (after reformating the reiser4 partition), and got no problem. Retried several times, and also from and to the xfs and ext3 partitions, no problem at all. did you do: cp /tmp_jfs/* /tmp_reiser4/? No, my iso images were in a subdirectory of /tmp_jfs so I did cp /tmp_jfs/isos/* /tmp_reiser4 (which was completely empty at start, btw). -- Damien Wyart
Re: Error messages.
Am Donnerstag, 6. März 2003 13:23 schrieb Anders Widman: Hardware is so much fun to debug sometimes, and when you are the 1% case life can really suck. Do you have: bad cooling Nope. Not warmer than 35C anywhere, including the surface of the drives. bad power supply Well, this has been checked too, though I could not be entirely sure. I have used two different Chieftek 340W PSUs bad voltage from power company The power distribution facility is just about 300m from here. And I have installed line filters that takes cares of noise and spikes. electrical noise How do I measure this?... Might be as there are many drives installed. They might disturb each other. ? I think though that Oleg is right that you should contact the IDE guys and ask them for their list of things to check for that particular error message (and tell us about it). Yes, I am trying to get contact with the linux-ide mailing list. We'll see what will come out of those. Prior experience with that list is not very successful ;) Maybe simple l-k? Or Alan Cox, Andre Hedrick directly? ;-) Regards, Dieter
RE: Error messages.
Anders, here is what I have and it works on thousands of duplicate servers: Tyan S2420 with 1.0GHz PIII 512MB RAM Promise PDC20269 in PCI1 Intel Dual 10/100 NIC in PCI2 Four Maxtor 250GB IDE drives off of the Promise controller lk 2.4.19 on RH7.3 hdparm -a64 -K1 -W1 -u1 -m16 -c1 -d1 /dev/hdx Regards, Wayne. -Original Message- From: Anders Widman [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 3:46 AM To: [EMAIL PROTECTED] Subject: Re: Error messages. On Wed, 2003-03-05 at 21:51, Anders Widman wrote: On Wed, Mar 05, 2003 at 08:18:18PM +0100, Anders Widman wrote: New Promise controllers PDC20268 (Ultra 100Tx2) does that mean you only tested on these pdc's ? I changed from Three Ultra100 to Ultra100Tx2. Now I only use two boards in this particular system. If so then then drop this damn PDC controller and get one that is supported under linux (e.g. hpt370 based controllers). I had the very same problems with these PDC20268 controllers. When I switched to anything above MDMA0 (note not even UDMA) the system was freezing from time to time. This happens here too... On the internal controller your drives should work all fine (via/intel chipsets work nicely), also on hpt based chipsets and also cmd is supporting linux... but forget about promise. This company just does not support linux. I was using kernels 2.4.19/20/21pre1/21pre4/21pre4-ac5 and all had the very same problem. When I heard from others that they had problems with promise I switched... and I am now enjoying a rock stable system. It might just have to come to this, but I do not want to buy new hardware :) Soeren. PGP public key: https://tnonline.net/secure/pgp_key.txt
Re: Error messages.
Anders, here is what I have and it works on thousands of duplicate servers: Tyan S2420 with 1.0GHz PIII 512MB RAM Promise PDC20269 in PCI1 Using PDC20268 Intel Dual 10/100 NIC in PCI2 Four Maxtor 250GB IDE drives off of the Promise controller lk 2.4.19 on RH7.3 hdparm -a64 -K1 -W1 -u1 -m16 -c1 -d1 /dev/hdx hm.. The big difference I see is -that I normally use -c3.
Re: Error messages.
Do you have apic enabled or disabled in both the kernel and the BIOS? Do you have acpi enabled or disabled in both the kernel and the BIOS? Yes, right now both are. Will be trying without. If it works it means there is a nasty bug in the kernel/or Promise drivers? Have now tried without ACPI,APIC and APM. Still crashes :( Will fiddle more with this in the weekend. PGP public key: https://tnonline.net/secure/pgp_key.txt
Re: Error messages.
In article [EMAIL PROTECTED],
Anders Widman [EMAIL PROTECTED] wrote:
This has come up on this list a number of times, and no one still
seem to have found the true answer to the problem.
kernel: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Most seem to say this is a bad block on the harddrive. I am not
convinced though. Using Linux on three machines here, and I have
seen this error on all of them, with lots of disks. The error seem
to come random, but does cause system lockups and broken
filesystems.
It's a timeout during a data request, which could be caused by a bad
block, but might also be caused by poor cabling, overheating, or crap
drive firmware. If there is a disk that appears to be implicated, the
real culprit could actually be caused by the _other_ disk on the cable,
if there is one. It's very hard to tell which of these is the case
without more information than this log message--all you know is that
suddenly the drive stops responding to commands, or that you can't
send commands to the drive any more.
You get data corruption because the usual way out of one of these
messages is a drive reset, which will discard any writes that might
have been buffered in the drive's controller but not written on the disk.
Linux might also get confused here, which just makes a bad situation
worse.
I had dozens of these messages every day before I started explicitly
cooling drives _and_ the drive controllers. For some reason board
manufacturers to this day do not put heat sinks on their ATA100 and
faster chips. I can only assume that this is because they assume your
machine will spend no more than 20% of its time doing disk I/O, and
design a system that will overheat if it does disk I/O continuously at
full speed for any length of time.
After I started aggressively cooling disks and controllers, I now only
see that message a few weeks before disks fail. Usually the 'smartctl'
utility (from smartsuite) will also list reallocated sectors in the
output of 'smartctl -v' (i.e. bad sectors that have been remapped).
Have about 20 disks, and have replaced and upgraded them several
times too. This error has shown on most of them. But when testing
them with tools like IBM DFT, Maxtor Powermax, badblocks or chkdsk
in Windows none show up to be with errors on.
Most vendor utilities will never report errors on a drive until the
disk has failed in some fatal way. It's against their interests to
do otherwise.
Sometimes it seem to help to disable DMA and or lower UDMA mode
(all drives are ATA-100 or ATA-133). But then after a few days, or
a few minutes the kernel starts spitting out these status=0x58
errors.
This happens to make the chips run cooler.
After looking online on different forums it does seem that many
people are experiencing them.
What exactly does this status=0x58 error mean, and what can one do
to solve the problem?
0x58 = 0x40 | 0x10 | 0x08 (i.e. the DriveReady, SeekComplete, and
DataRequest bits). Usually this is followed by an error message from
the last command that was sent to the drive (e.g.
end_request: I/O error, dev 03:42 (hdb), sector 69234536
).
--
Zygo Blaxell (Laptop) [EMAIL PROTECTED]
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD
Re: Error messages.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anders Widman wanted us to know: Have now tried without ACPI,APIC and APM. Still crashes :( Will fiddle more with this in the weekend. Get the absolute latest Cooker kernel. For what it's worth, I've heard that RedHat's kernels work well with the PDC chipsets, so you might try with their latest from their Beta as well. - -- Blue skies... Todd | Get a bigger hammer! | Are you feeling lucky...punk? | | http://www.mrball.net | I've had better days... | | http://faq.mrball.net | It's the end of the world as we know i| Linux kernel 2.4.19-24mdk load average: 0.00, 0.04, 0.00 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: http://www.mrball.net/todd.asc iD8DBQE+aDMSIBT1264ScBURAjDSAJ4zrTIW67XJPkjL0jn8fwew1HCERgCeJq2R +pV0MM+C8F1mbI9Hkdafw8A= =QjxQ -END PGP SIGNATURE-
