Re: Hard disk crash and solution
Zygo Blaxell wrote: In article [EMAIL PROTECTED], Niek [EMAIL PROTECTED] wrote: Title: IBM DTLA 307045 Hard disk crash I bought this disk (46 GB) about two years ago. One of the best they claimed. [...] What is the fucking MBTF of these drives?? Is it close to one year like I experienced? My employer used a total of 13 of these drives (various sizes, but all the same family) for RAID arrays. We originally purchased 10, and replaced the first 3 to die under IBM warranty. After the first 3, we started replacing dead disks with some other brand of drive. In the end 9 of the IBM drives died. Some days two or three disks would fail at a time. We didn't bother waiting for the last 4, but presumably they would have died if we hadn't replaced all of them. We took the rest of them apart to use as cubicle wall decorations, shaving mirrors, etc. Even worse, for about 6 hours before some of them died, they randomly flipped a few bits here and there in the data, which made RAID redundancy useless. Maybe we should warn against them in our FAQ? -- Hans
Re: mkreiserfs -s 1024 makes unmountable partitions
Oleg Drokin wrote: Hello! On Mon, Jan 27, 2003 at 02:20:47AM -0500, Scott R. Every wrote: this URL works better: ftp://ftp.suse.com/pub/people/mason/patches/data-logging Oleg, thanks so much for this info(and Chris, thanks for the patches). This is much needed for embedded filesystems of 128MB and smaller. Its hard to fit a 32MB journal on a 32 or 16MB FLASH disk! Actually if you have direct access to FLASH device (e.g. through MTD), then you really want to look at jffs2. Besides being journalled, it also provides data compression (which is invaluable for such small storage sizes) and flash wearing control (or what is the name for facility that controls that certain areas of flash are not written to more often then other ones). Bye, Oleg Reiser4 will provide compression (compression plugin is being coded now), and won't waste space for a mandatory fixed size journal area. -- Hans
What Filesystem?
Dear Sirs, I am a visual artist and musician. As well as a range of traditional media I use Linux Mandrake 8.0 on an old Athlon-based PC. I wrote to Mr. Hans Reiser, after following a mailto link on the Namesys website, with a slightly lengthier version of the question written below, and was advised that This is really a better question for our mailing list ([EMAIL PROTECTED]) than for me, as I am obviously biased. I am therefore sending this email to you in the hope that somebody may be able to solve my puzzle - or at least direct me towards another knowledgeable source of information! Thank you. The question: ... I have done much research in the field of computer /hardware/ suitable for commercial Digital Content Creation (P4 Xeon; Wildcat graphics; ART's PURE raytracing PCI render board, etc. ...) and now look to a better understanding of the choices I might make for a (presumably) Linux-based OS running on (presumably) Intel 32-bit hardware SUCH AS these two elements:- 1. Kernel Patches - pre-empt and low latency; 2. File System type - EXT3, ReiserFS, SGi's XFS, HFS, JFS; Would you be able to advsie me on any issues I might need to be aware of and perhaps any firm decisions you think would be good for me to make, regarding OS choice and configuration? I realise that all pre-built workstations supplied by Dell, IBM and HP-Compaq come with RedHat, but, just for the record, I like Mandrake and I am getting into the WindowMaker desktop :). I also develop my website locally using Apache (but hosted on Freeserve :( ), and I understand pre-empt /or low-latency patches are counter-effective for servers. However, as long as no real harm can be expected, my priority is for graphics and sound creation, editing, compositing, publishing, etc., while fast response for just developing html pages isn't. I would like to believe that, somewhere, I can get a 'standard' Linux patched for optimal DCC, with suitable FS type available to choose from during installation. If not, I will have to find and apply patches, but I know that with FS type any change demands a reformat, which can really disrupt a working week! [End question] Yours faithfully, James Thompson, Visual Artist Musician H.E. Student of Fine Arts
Re: What Filesystem?
On Wed, Jan 29, 2003 at 03:20:26PM -0500, James Thompson wrote: I am a visual artist and musician. Check out the document at http://myweb.cableone.net/eviltwin69/ALSA_JACK_ARDOUR.html. There a section that benchmarks various filesystems for their latency. The short story is that Reiserfs wins handily over Ext2, Ext3, and FAT32 (duh! why would someone test that...). Unfortunately, there's no comparison between Reiser/JFS/XFS. I think that would be more of a fair match. Anyhow though, for general low-latency multimedia work, ReiserFS looks like it's a good choice. -- Ross Vandegrift [EMAIL PROTECTED] A Pope has a Water Cannon. It is a Water Cannon. He fires Holy-Water from it.It is a Holy-Water Cannon. He Blesses it. It is a Holy Holy-Water Cannon. He Blesses the Hell out of it. It is a Wholly Holy Holy-Water Cannon. He has it pierced.It is a Holey Wholly Holy Holy-Water Cannon. He makes it official. It is a Canon Holey Wholly Holy Holy-Water Cannon. Batman and Robin arrive. He shoots them.
Re: What Filesystem?
On Wed, Jan 29, 2003 at 03:20:26PM -0500, James Thompson wrote: I am a visual artist and musician. Check out the document at http://myweb.cableone.net/eviltwin69/ALSA_JACK_ARDOUR.html. There a section that benchmarks various filesystems for their latency. The short story is that Reiserfs wins handily over Ext2, Ext3, and FAT32 (duh! why would someone test that...). Simply because FAT filesystem is very simple and has little overhead. If dealing with little amount of files and folders then it can be rather quick, especially if you need CPU resources to other things. Unfortunately, there's no comparison between Reiser/JFS/XFS. I think that would be more of a fair match. Anyhow though, for general low-latency multimedia work, ReiserFS looks like it's a good choice.
Re: What Filesystem?
Reiserfs is probably not what you want for doing lots of high volume data. Reiserfs is good with many small files and general purpose use. It is actually the slowest filesystem for bulk data. I'm sure some smartass will probably post some benchmark to prove me wrong, but SGI have a long heritage of making filesystems for exactly what you want and so if XFS works I'd say use that. It's pumpin'. Of course more quantitative comparisons can easily be found on the linux-kernel mailing list. However, the practical difference between the high performance filesystems you mentioned, or the difference between running pre-empt or not should be considered marginal compared to other factors - such as, the load that your hard disk controller places on the system and the number of physical disks you have (and how many RPM they run at). Keep in mind that you can often nearly double the data throughput of a system by doubling the number of physical disks in it, and using RAID. Even with the latest UDMA-133, I haven't seen any IDE system actually perform without bothering the CPU non-trivially (of course YMMV). Using SCSI disks and controllers will give you a smoother system ride; which is why 95% of high-end workstations come equipped with SCSI. You can get 15,000 RPM U320 SCSI disks, which are f*** fast (though loud). This is largely because the SCSI protocol was designed properly, IDE/ATA is a hack. Serial-ATA promises to offer SCSI like host efficiency, but I'll only believe it when I see it. And at the moment the costs are as bad as SCSI anyway. Of course, being able to move around large chunks of data quickly extends to other parts of the system, too. The bigger and faster the system BUS, the better. Having `researched hardware platforms' you should know this, of course. As far as Athlon Motherboards go, Tyan are a reputable vendor who used to produce Sun clone motherboards - they have a really nice dual capable system with dual U160 SCSI controllers and 66MHz PCI slots - which must mean that the SCSI controllers run at that speed. It's definitely worth the ~$500 price tag. They all pale in comparison to R1+ based SGI or Sparc 9+ platforms of course. From a graphic artist's perspective, you're probably better off buying a new G4 based system and running MacOS X, you know :-). Linux isn't exactly `The Platform' for digital content creation. The Mac's CPU and hardware platform are a lot better at moving data around, and if you've got a Mac then you can run Mac OS X, or Linux + Mac OS inside an emulator (which runs FAST!). As a final note, keep in mind that a filesystem reformat does not mean a re-install; keep your partitions as small as practical and you can change them over individually. Sam. On Thu, 30 Jan 2003 09:20, James Thompson wrote: Dear Sirs, I am a visual artist and musician. As well as a range of traditional media I use Linux Mandrake 8.0 on an old Athlon-based PC. I wrote to Mr. Hans Reiser, after following a mailto link on the Namesys website, with a slightly lengthier version of the question written below, and was advised that This is really a better question for our mailing list ([EMAIL PROTECTED]) than for me, as I am obviously biased. I am therefore sending this email to you in the hope that somebody may be able to solve my puzzle - or at least direct me towards another knowledgeable source of information! Thank you. The question: ... I have done much research in the field of computer /hardware/ suitable for commercial Digital Content Creation (P4 Xeon; Wildcat graphics; ART's PURE raytracing PCI render board, etc. ...) and now look to a better understanding of the choices I might make for a (presumably) Linux-based OS running on (presumably) Intel 32-bit hardware SUCH AS these two elements:- 1. Kernel Patches - pre-empt and low latency; 2. File System type - EXT3, ReiserFS, SGi's XFS, HFS, JFS; Would you be able to advsie me on any issues I might need to be aware of and perhaps any firm decisions you think would be good for me to make, regarding OS choice and configuration? I realise that all pre-built workstations supplied by Dell, IBM and HP-Compaq come with RedHat, but, just for the record, I like Mandrake and I am getting into the WindowMaker desktop :). I also develop my website locally using Apache (but hosted on Freeserve :( ), and I understand pre-empt /or low-latency patches are counter-effective for servers. However, as long as no real harm can be expected, my priority is for graphics and sound creation, editing, compositing, publishing, etc., while fast response for just developing html pages isn't. I would like to believe that, somewhere, I can get a 'standard' Linux patched for optimal DCC, with suitable FS type available to choose from during installation. If not, I will have to find and apply patches, but I know that with FS type any change demands a
Re: Fwd: Re: Segmentation Fault when mounting ataraid
Well, that certainly looks like a bug in mount options parsing code. Edward and Oleg, please review and fix. Hans Manuel Krause wrote: Hi! Just forwarding... the ksymoopsed version. Please, send any hints and solutions or other comments to Jochens address [EMAIL PROTECTED] . Manuel Original Message From: - Tue Jan 28 20:56:55 2003 Date: Tue, 28 Jan 2003 20:47:29 +0100 From: Jochen Haemmerle [EMAIL PROTECTED] User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) To: Manuel Krause [EMAIL PROTECTED] Subject: Re: Segmentation Fault when mounting ataraid References: [EMAIL PROTECTED] [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] Well, down there it is!! thx for the quick answers Bye, Jochen Manuel Krause wrote: On 01/27/2003 11:30 PM, Jochen Haemmerle wrote: Hello! When I try to mount my reiserfs partition on a HPT370 Stripe I get a Segmentation Fault. All other partitions (reiserfs of cource) work fine. My kernel is the 2.4.20 from Kernel.org The PC is a Dual PIII 866 with Via-Apollo Chipset The Harddisks are 2 Maxtor 80GB ACPI is turned off ! I don't know if this error depends on reiserfs, but maybe someone can help me! Best Regards Jochen Haemmerle Can you process it through something like: cat this-segfault.txt | ksymoops -m /boot/System.map-you.had@segfault and post the result ... while awaiting the developers' answer?! This would provide essentially more info for them (even if they knew the BUG already), AFAIK. Bye, Manuel guardian@viking:~$ cat segfault.txt | ksymoops -m /boot/System.map-2.4.20 ksymoops 2.4.6 on i686 2.4.20. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.20/ (default) -m /boot/System.map-2.4.20 (specified) Unable to handle kernel NULL pointer dereference at vitual address 0004 c01a62c0 *pde = Oops: 0002 CPU: 0 EFLAGS: 00010012 eax: ebx: c03324f8 ecx: dff188a0 edx: c03324fc esi: edi: c03324f8 ebp: 0008 esp: d7839d98 Process mount (pid: 327, stackpage=d7839000) 007c 098a9f2d c0332518 0800 c0332520 c0332518 0080 003e003f c01a6c6c c03324f8 d7cc54a0 0008 Call Trace: [c01a698d] [c01a6c6c][c01a6ccc] [c01a6e27] [c0172671] [c0173188] [c013c712] [c014d546][c013c8fd] [c014e589] [c014e842] [c014e6ad] [c014ec6f] [c0106f17] Code: 89 50 04 89 02 c7 01 00 00 00 00 c7 41 04 00 00 00 00 ff 0b Using defaults from ksymoops -t elf32-i386 -a i386 ebx; c03324f8 parse_options+124/1c8 edx; c03324fc parse_options+128/1c8 edi; c03324f8 parse_options+124/1c8 Trace; c01a698d reiserfs_super_in_proc+69/254 Trace; c01a6c6c reiserfs_per_level_in_proc+f4/134 Trace; c01a6ccc reiserfs_bitmap_in_proc+20/a0 Trace; c01a6e27 reiserfs_on_disk_super_in_proc+db/f0 Trace; c0172671 nlm_shutdown_hosts+e9/11c Trace; c0173188 nlmsvc_lock+c8/340 Trace; c013c712 sys_getdents64+7e/b3 Trace; c014d546 notesize+1e/2c Trace; c013c8fd max_select_fd+9d/a4 Trace; c014e589 handle_ide_mess+25/194 Trace; c014e842 msdos_partition+14a/2f8 Trace; c014e6ad handle_ide_mess+149/194 Trace; c014ec6f __load_block_bitmap+17f/198 Trace; c0106f17 show_stack+7/78 Code; Before first symbol _EIP: Code; Before first symbol 0: 89 50 04 mov%edx,0x4(%eax) Code; 0003 Before first symbol 3: 89 02 mov%eax,(%edx) Code; 0005 Before first symbol 5: c7 01 00 00 00 00 movl $0x0,(%ecx) Code; 000b Before first symbol b: c7 41 04 00 00 00 00 movl $0x0,0x4(%ecx) Code; 0012 Before first symbol 12: ff 0b decl (%ebx) -- Hans
Re: What Filesystem?
On Wed, 29 Jan 2003 15:20:26 EST, James Thompson [EMAIL PROTECTED] said: ... I have done much research in the field of computer /hardware/ suitable for commercial Digital Content Creation (P4 Xeon; Wildcat graphics; ART's PURE raytracing PCI render board, etc. ...) and now Hmm.. so we're looking at high-end rendering, which is usually a CPU hog. 1. Kernel Patches - pre-empt and low latency; so I'm not clear on why you're worried about low latency? Remember that it *does* come with an overhead - the low-latency stuff is good if you're more concerned about fast response than total system load (for instance, on my laptop I'm willing to give up 5% of the CPU if it makes the X server run perceivably faster. If I was doing a lot of rendering, I'd want that 5% for user cycles. Could you be more specific regarding what sort of content you are making? (i.e. single frame images suitable for monitor display (1600x1200 and smaller), or large-format for high-resolution printing (posters, etc), or video, etc..) The resources needed to produce a 10-minute video clip are different from the things you'll need to produce a 4 foot x 5 foot poster at 600DPI. -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech msg07439/pgp0.pgp Description: PGP signature
Re: Segmentation Fault when mounting ataraid
So, here it comes again! Don't care about the warning this is the machine the errror occures! I hope someone understands that sh*** because I don't!!! Yesterday I've patched my Kernel to 2.4.21-pre3. The bug does not appear! It seems to be only a bug of the 2.4.20 (on 2.4.19 it works too...as I allready mentioned here) For me so far, is the way it works, ok, but if the abitions of someone have no limit, your welcome to mail me if you need informations about my PC. Thx for all helping answers!! Bye Jochen Haemmerle ksymoops 2.4.6 on i686 2.4.20. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.20/ (default) -m /boot/System.map-2.4.20 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Unable to handle kernel NULL pointer dereference at vitual address 0004 c01a62c0 *pde = Oops: 0002 CPU: 0 EIP: 0010:[c01a62c0]Tainted: P Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010012 eax: ebx: c03324f8 ecx: dff188a0 edx: c03324fc esi: edi: c03324f8 ebp: 0008 esp: d7839d98 Process mount (pid: 327, stackpage=d7839000) 007c 098a9f2d c0332518 0800 c0332520 c0332518 0080 003e003f c01a6c6c c03324f8 d7cc54a0 0008 Call Trace: [c01a698d] [c01a6c6c][c01a6ccc] [c01a6e27] [c0172671] [c0173188] [c013c712] [c014d546][c013c8fd] [c014e589] [c014e842] [c014e6ad] [c014ec6f] [c0106f17] Code: 89 50 04 89 02 c7 01 00 00 00 00 c7 41 04 00 00 00 00 ff 0b EIP; c01a62c0 get_request+24/54 = ebx; c03324f8 ide_hwifs+858/21e8 ecx; dff188a0 _end+1fbca488/20962c48 edx; c03324fc ide_hwifs+85c/21e8 edi; c03324f8 ide_hwifs+858/21e8 esp; d7839d98 _end+174eb980/20962c48 Trace; c01a698d __make_request+3f5/5b4 Trace; c01a6c6c generic_make_request+120/130 Trace; c01a6ccc submit_bh+50/70 Trace; c01a6e27 ll_rw_block+13b/1a4 Trace; c0172671 read_bitmaps+c1/1ac Trace; c0173188 reiserfs_read_super+120/4a4 Trace; c013c712 get_sb_bdev+1de/258 Trace; c014d546 alloc_vfsmnt+76/a0 Trace; c013c8fd do_kern_mount+55/104 Trace; c014e589 do_add_mount+69/138 Trace; c014e842 do_mount+146/160 Trace; c014e6ad copy_mount_options+55/a4 Trace; c014ec6f sys_mount+af/110 Trace; c0106f17 system_call+33/38 Code; c01a62c0 get_request+24/54 _EIP: Code; c01a62c0 get_request+24/54 = 0: 89 50 04 mov%edx,0x4(%eax) = Code; c01a62c3 get_request+27/54 3: 89 02 mov%eax,(%edx) Code; c01a62c5 get_request+29/54 5: c7 01 00 00 00 00 movl $0x0,(%ecx) Code; c01a62cb get_request+2f/54 b: c7 41 04 00 00 00 00 movl $0x0,0x4(%ecx) Code; c01a62d2 get_request+36/54 12: ff 0b decl (%ebx) 1 warning issued. Results may not be reliable.
Re: What Filesystem?
Am Mittwoch, 29. Januar 2003 16:28 schrieb Ross Vandegrift: On Wed, Jan 29, 2003 at 03:20:26PM -0500, James Thompson wrote: I am a visual artist and musician. Check out the document at http://myweb.cableone.net/eviltwin69/ALSA_JACK_ARDOUR.html. There a section that benchmarks various filesystems for their latency. The short story is that Reiserfs wins handily over Ext2, Ext3, and FAT32 (duh! why would someone test that...). Unfortunately, there's no comparison between Reiser/JFS/XFS. I think that would be more of a fair match. XFS could win _today_ for real time (granted video bandwidth, for which it was designed in the first place), but this could change (compensate) with the latest ReiserFS 3.x patches (data logging) and finally Reiser4 (see the Reiser Homepage). Anyhow though, for general low-latency multimedia work, ReiserFS looks like it's a good choice. Yes. Go with low-latency _and_ preemption patches (try Gentoo, it has it all). I did beta testing for Robert Love (MontaVista) for ages and it is _the way to go_ for multi media machines. Greetings, Dieter -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: Dieter.Nuetzel at hamburg.de (replace at with @)
Re: UNSUBSCRIBE PLEASE THANKS - add a footer, please
Tue, Jan 28, 2003 at 10:14:11AM +0100, Szabolcs Szasz wrote: You're using Ximian Evolution: View - MessageDisplay - ShowFullHeaders Few people ever see those headers. Having full headers on is not a realistic assumption, ESPECIALLY NOT for those (mostly beginners), who have unsubscribe problems. A footer, maybe? instructions on web-site. much more realistical. including auto-helpdesk and my address for especially tough cases. :) Sab -- Cache remedies via multi-variable logic shorts will leave you crying.(cl) Lex Lyamin
Re: Oh no! Not again!
OK. So I built the latest reiserfsck as a static binary, and ran it with --rebuild-tree, and I got an infinite loop just like previously. In case anyone cares, I have kept the logfile for it. Is there anything that interests you about that failure, or should I promptly reformat the disk? Also, does any of you have any hint as to how to identify the failure that led to this crash? I suspect either the disk or the motherboard, but it's hard to tell: booting on my 80MB rescue disk works well, whereas the disk looks like it works correctly on another machine, and does not issue errors even on that machine, if I don't use DMA. Really weird. What scares me is that if I don't identify the problem, a similar crash may happen again... Cheers! [ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ] [ TUNES project for a Free Reflective Computing System | http://tunes.org ] Demand the establishment of the government in its rightful home at Disneyland.
Re: What Filesystem?
Am Mittwoch, 29. Januar 2003 19:16 schrieb [EMAIL PROTECTED]: On Wed, 29 Jan 2003 15:20:26 EST, James Thompson [EMAIL PROTECTED] said: ... I have done much research in the field of computer /hardware/ suitable for commercial Digital Content Creation (P4 Xeon; Wildcat graphics; ART's PURE raytracing PCI render board, etc. ...) and now Hmm.. so we're looking at high-end rendering, which is usually a CPU hog. 1. Kernel Patches - pre-empt and low latency; so I'm not clear on why you're worried about low latency? Remember that it *does* come with an overhead What? --- Sorry, quantify it. I can't. All low latency and pre-emption tests have showed _improved_ throughput (Yes) and much better multi media (video/audio) experience ;-) No measurable overhead an single and SMP systems (both Athlon). That's why it is in 2.5/2.6. - the low-latency stuff is good if you're more concerned about fast response than total system load (for instance, on my laptop I'm willing to give up 5% of the CPU if it makes the X server run perceivably faster. If I was doing a lot of rendering, I'd want that 5% for user cycles. But you want to have the much better task switching behavior together with the brand new O(1) scheduler. Could you be more specific regarding what sort of content you are making? (i.e. single frame images suitable for monitor display (1600x1200 and smaller), or large-format for high-resolution printing (posters, etc), or video, etc..) The resources needed to produce a 10-minute video clip are different from the things you'll need to produce a 4 foot x 5 foot poster at 600DPI. You mean single vs 2-/4-/8-/etc. (NUMA) SMP systems or even clusters? ;-) Greetings, Dieter -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: Dieter.Nuetzel at hamburg.de (replace at with @)
Re: What Filesystem?
On Wed, 29 Jan 2003 20:43:38 +0100, Dieter =?iso-8859-1?q?N=FCtzel?= said: All low latency and pre-emption tests have showed _improved_ throughput (Yes) and much better multi media (video/audio) experience ;-) No measurable overhead an single and SMP systems (both Athlon). That's why it is in 2.5/2.6. Yes, but my *point* was that if the box is busy doing a 5-hour rendering job, the low-latency *wont make a difference*. If you're doing audio work or video captures, yes the low-latency/preempt stuff will help. If you're in a single thread that's CPU-bound, there's no need to go installing 2.5 to get it. But you want to have the much better task switching behavior together with the brand new O(1) scheduler. You want that *if* the actual load will benefit from it. See my comment above about rendering... You mean single vs 2-/4-/8-/etc. (NUMA) SMP systems or even clusters? ;-) Some things are doable with a single CPU, some things need the NUMA stuff, other things can use a Beowulf. Thus the need to quantify what the actual requirements are. Video editing will bottleneck on different things than photorealistic rendering of graphics. -- Valdis Kletnieks Computer Systems Senior Engineer Virginia Tech msg07446/pgp0.pgp Description: PGP signature
Re: Oh no! Not again!
On Wednesday 29 January 2003 22:31, Francois-Rene Rideau wrote: OK. So I built the latest reiserfsck as a static binary, and ran it with --rebuild-tree, and I got an infinite loop just like previously. In case anyone cares, I have kept the logfile for it. Is there anything that interests you about that failure, or should I promptly reformat the disk? Did you run the fsck (booted from /boot) when the drive was in that other mashine you had no problem with or in the problem one? It is a bad idea to run reiserfsck on a broken hardware - the result is unpredictable. Also, does any of you have any hint as to how to identify the failure that led to this crash? I suspect either the disk or the motherboard, If you do not see any problem with the disk when you put it into another computer - it is not the disk. It can be IDE controller, cable... but it's hard to tell: booting on my 80MB rescue disk works well, whereas the disk looks like it works correctly on another machine, and does not issue errors even on that machine, if I don't use DMA. Really weird. What scares me is that if I don't identify the problem, a similar crash may happen again... Cheers! [ François-René ÐVB Rideau | ReflectionCybernethics | http://fare.tunes.org ] [ TUNES project for a Free Reflective Computing System | http://tunes.org ] Demand the establishment of the government in its rightful home at Disneyland. -- Thanks, Vitaly Fertman
Re: Fwd: Re: Segmentation Fault when mounting ataraid
Hello! On Wed, Jan 29, 2003 at 08:38:16PM +0300, Hans Reiser wrote: Well, that certainly looks like a bug in mount options parsing code. Edward and Oleg, please review and fix. There is another decoded output that makes much more sence to me. And it suggest something gone wrong within block layer. (And in the one you are referring to parse_options's address is only stored in registers, not in bactrace. Also starting from 2.4.20, there is no function named parse_optinos in reiserfs code). Bye, Oleg
Re: Segmentation Fault when mounting ataraid
Hello! On Wed, Jan 29, 2003 at 07:32:31PM +0100, Jochen Haemmerle wrote: So, here it comes again! Don't care about the warning this is the machine the errror occures! I hope someone understands that sh*** because I don't!!! Ok, looks like __make_request tries to call get_request, and there is something wrong with request queue. Yesterday I've patched my Kernel to 2.4.21-pre3. The bug does not appear! It seems to be only a bug of the 2.4.20 (on 2.4.19 it works too...as I allready mentioned here) Well, that probably means there was some bug in 2.4.20, that is now fixed in ataraid code path in later kernel, I presume. Though I quckly scanned changelogs and see nothing related. Bye, Oleg
