Re: 2.6.15.1+reiser4 Kernel Panic
Hello On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: > Hi, > > i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from > ftp.namesys.com, when writing data to a usb harddisk. > > kernel output: > loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom > (fs/reiser4/txnmgr.c:1130)[zam-597] > write log failed (-5) > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom > (fs/reiser4/txnmgr.c:1130)[zam-597] > write log failed (-5) > > and the machine is *frozen* > > the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's a > reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 is > running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is clear. > can you reproduce the problem? > Best Regards, > Patrick > >
Re: 2.6.15.1+reiser4 Kernel Panic
Hi,
i have the same Problem witch 2.6.16-rc1 with the reiser4 Patch from
ftp.namesys.com.
Same error and the System is frozen to. But I wanted to copy data from
Partition A (Reiser3) to Partition B (Reiser4).
greets
Jan
From: "Vladimir V. Saveliev" <[EMAIL PROTECTED]>
To: Ps <[EMAIL PROTECTED]>
Date: Mon, 30 Jan 2006 11:29:18 +0300
Subject: Re: 2.6.15.1+reiser4 Kernel Panic
Hello
On Sun, 2006-01-29 at 11:44 +0100, Ps wrote:
> Hi,
>
> i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from
> ftp.namesys.com, when writing data to a usb harddisk.
>
> kernel output:
> loop4: loop_end_io_transfer err=-95 bi_rw=0x5
> reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom
> (fs/reiser4/txnmgr.c:1130)[zam-597]
> write log failed (-5)
>
> reiser4 panicked cowardly: reiser4[pdflush(6748)]:
commit_current_atom
> (fs/reiser4/txnmgr.c:1130)[zam-597]
> write log failed (-5)
>
> and the machine is *frozen*
>
> the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's a
> reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 is
> running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is
clear.
>
can you reproduce the problem?
> Best Regards,
> Patrick
>
>
"Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken"
www.klarmobil.de/index.html?pid=73025
Re: 2.6.15.1+reiser4 Kernel Panic
so after i've forgot to include the list, the message again + a view new lines Am Montag, den 30.01.2006, 14:06 +0300 schrieb Vladimir V. Saveliev: > Hello > > On Mon, 2006-01-30 at 11:11 +, Ps wrote: > > Am Montag, den 30.01.2006, 11:29 +0300 schrieb Vladimir V. Saveliev: > > > Hello > > > > > > On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: > > > > Hi, > > > > > > > > i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from > > > > ftp.namesys.com, when writing data to a usb harddisk. > > > > > > > > kernel output: > > > > loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > > > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom > > > > (fs/reiser4/txnmgr.c:1130)[zam-597] > > > > write log failed (-5) > > > > > > > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom > > > > (fs/reiser4/txnmgr.c:1130)[zam-597] > > > > write log failed (-5) > > > > > > > > and the machine is *frozen* > > > > > > > > the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's a > > > > reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 is > > > > running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is clear. > > > > > > > > > > can you reproduce the problem? > > Yes, everytime i write on this partition (ok i've only testet a view files, > > but when i delete one file and it syncs, it always crashes. deleting with > > kernel 2.6.13.4 and loop-aes 3.1c makes no problem) > > > > May I ask you to try this if filesystem is ext2, please? no chance at the moment, I don't have enough free discspace for testing. but maybe i get tomorrow a temporary disk for copying data on. if it help's the root on laptop runs without an error (also encrypted), but the root on the desktop has the same problem and doesn't boot (wenn bootlogd tries to write data it hangs) :-/ then I've got another machine (i386, the laptop and desktop are x86_64) which has an reiserfs 3.6 on the loop => runs also without a warning or crash. (with 2.6.15.2) a harddisk problem like on jan's machine is nearly impossible, because it runs perfekt with the 2.6.13 kernel and the desktop relies on an raid5, so a bad sector should be reported in the raid status (smart status also good) has anyone an idea what I could check? > > > > Best Regards, > > > > Patrick > > > > > > > > > > > > > > > > > > > >
Re: 2.6.15.1+reiser4 Kernel Panic
Hello, On Sunday 29 January 2006 13:44, Ps wrote: > Hi, > > i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from > ftp.namesys.com, when writing data to a usb harddisk. please try to mount reiser4 volume with "no_write_barrier" option. > > kernel output: > loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > reiser4 panicked cowardly: reiser4[pdflush(6748)]: > commit_current_atom (fs/reiser4/txnmgr.c:1130)[zam-597] > write log failed (-5) > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: > commit_current_atom (fs/reiser4/txnmgr.c:1130)[zam-597] > write log failed (-5) > > and the machine is *frozen* > > the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's a > reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 is > running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is > clear. > > Best Regards, > Patrick -- Alex.
Re: 2.6.15.1+reiser4 Kernel Panic
Hi, this seems to work... Am Freitag, den 24.03.2006, 17:04 +0300 schrieb Alexander Zarochentsev: > Hello, > > On Sunday 29 January 2006 13:44, Ps wrote: > > Hi, > > > > i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from > > ftp.namesys.com, when writing data to a usb harddisk. > > please try to mount reiser4 volume with "no_write_barrier" option. > > > > > kernel output: > > loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: > > commit_current_atom (fs/reiser4/txnmgr.c:1130)[zam-597] > > write log failed (-5) > > > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: > > commit_current_atom (fs/reiser4/txnmgr.c:1130)[zam-597] > > write log failed (-5) > > > > and the machine is *frozen* > > > > the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's a > > reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 is > > running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is > > clear. > > > > Best Regards, > > Patrick >
Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
i'm again... here are some more informations. i haven't encrypted my data and the error above the reiser4 panic is: end_request: I/O error, dev sdb, sector 64412 hope thats help finding the bug greets Jan - weitergeleitete Nachricht - Subject: Re: 2.6.15.1+reiser4 Kernel Panic Date: Di 31 Jan 2006 01:49:38 CET From: [EMAIL PROTECTED] > Hi, > i have the same Problem witch 2.6.16-rc1 with the reiser4 Patch from > ftp.namesys.com. > Same error and the System is frozen to. But I wanted to copy data from > Partition A (Reiser3) to Partition B (Reiser4). > > greets > > Jan > > From: "Vladimir V. Saveliev" <[EMAIL PROTECTED]> > To: Ps <[EMAIL PROTECTED]> > Date: Mon, 30 Jan 2006 11:29:18 +0300 > Subject: Re: 2.6.15.1+reiser4 Kernel Panic > Hello > > On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: > > Hi, > > > > i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from > > ftp.namesys.com, when writing data to a usb harddisk. > > > > kernel output: > > loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: > commit_current_atom > > (fs/reiser4/txnmgr.c:1130)[zam-597] > > write log failed (-5) > > > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: > commit_current_atom > > (fs/reiser4/txnmgr.c:1130)[zam-597] > > write log failed (-5) > > > > and the machine is *frozen* > > > > the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's > a > > reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 > is > > running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is > clear. > > > > can you reproduce the problem? > > > Best Regards, > > Patrick > > > > > > > > > "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" > www.klarmobil.de/index.html?pid=73025 > > weitergeleitete Nachricht Ende "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" www.klarmobil.de/index.html?pid=73025
Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
Wow, are we at last actually stable enough that hardware errors are more of a problem than software errors for our Reiser4 users? Rudekjan, you have a bad sector, buy a new drive, use dd_rescue to copy to it, don't run reiser4.fsck until you get the data onto the new drive. Why buy a new drive? Because after the first user visible bad sector, your odds of more bad sectors over time go WAY up. Your time+data are too valuable. Hans [EMAIL PROTECTED] wrote: >i'm again... here are some more informations. i haven't encrypted my data and >the error above the reiser4 panic is: > >end_request: I/O error, dev sdb, sector 64412 > >hope thats help finding the bug > >greets > >Jan > >- weitergeleitete Nachricht ----- > > >Subject: Re: 2.6.15.1+reiser4 Kernel Panic >Date: Di 31 Jan 2006 01:49:38 CET >From: [EMAIL PROTECTED] > > > >>Hi, >>i have the same Problem witch 2.6.16-rc1 with the reiser4 Patch from >>ftp.namesys.com. >>Same error and the System is frozen to. But I wanted to copy data from >>Partition A (Reiser3) to Partition B (Reiser4). >> >>greets >> >>Jan >> >>From: "Vladimir V. Saveliev" <[EMAIL PROTECTED]> >>To: Ps <[EMAIL PROTECTED]> >>Date: Mon, 30 Jan 2006 11:29:18 +0300 >>Subject: Re: 2.6.15.1+reiser4 Kernel Panic >>Hello >> >>On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: >>> Hi, >>> >>> i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from >>> ftp.namesys.com, when writing data to a usb harddisk. >>> >>> kernel output: >>> loop4: loop_end_io_transfer err=-95 bi_rw=0x5 >>> reiser4 panicked cowardly: reiser4[pdflush(6748)]: >>commit_current_atom >>> (fs/reiser4/txnmgr.c:1130)[zam-597] >>> write log failed (-5) >>> >>> reiser4 panicked cowardly: reiser4[pdflush(6748)]: >>commit_current_atom >>> (fs/reiser4/txnmgr.c:1130)[zam-597] >>> write log failed (-5) >>> >>> and the machine is *frozen* >>> >>> the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's >>a >>> reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 >>is >>> running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is >>clear. >>> >> >>can you reproduce the problem? >> >>> Best Regards, >>> Patrick >>> >>> >> >> >> >> >>"Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" >>www.klarmobil.de/index.html?pid=73025 >> >> >> >> > > > > weitergeleitete Nachricht Ende > > > > >"Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" >www.klarmobil.de/index.html?pid=73025 > > > > >
Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
To amplify what Hans (accurately) wrote, once you see bad sectors, that means that you already have many more than you see, and that your hard drive is all out of spare sectors to silently swap out for when it finds one. Basically, there's so much wrong with the surface that your hard drive can't hide any more flaws, and has given up trying. Hans is right: If you see a single bad sector, the drive is considered unsafe and trash for even the tightest owner. --Clay Hans Reiser wrote: Wow, are we at last actually stable enough that hardware errors are more of a problem than software errors for our Reiser4 users? Rudekjan, you have a bad sector, buy a new drive, use dd_rescue to copy to it, don't run reiser4.fsck until you get the data onto the new drive. Why buy a new drive? Because after the first user visible bad sector, your odds of more bad sectors over time go WAY up. Your time+data are too valuable. Hans [EMAIL PROTECTED] wrote: i'm again... here are some more informations. i haven't encrypted my data and the error above the reiser4 panic is: end_request: I/O error, dev sdb, sector 64412 hope thats help finding the bug greets Jan - weitergeleitete Nachricht - Subject: Re: 2.6.15.1+reiser4 Kernel Panic Date: Di 31 Jan 2006 01:49:38 CET From: [EMAIL PROTECTED] Hi, i have the same Problem witch 2.6.16-rc1 with the reiser4 Patch from ftp.namesys.com. Same error and the System is frozen to. But I wanted to copy data from Partition A (Reiser3) to Partition B (Reiser4). greets Jan From: "Vladimir V. Saveliev" <[EMAIL PROTECTED]> To: Ps <[EMAIL PROTECTED]> Date: Mon, 30 Jan 2006 11:29:18 +0300 Subject: Re: 2.6.15.1+reiser4 Kernel Panic Hello On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: > Hi, > > i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch from > ftp.namesys.com, when writing data to a usb harddisk. > > kernel output: > loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom > (fs/reiser4/txnmgr.c:1130)[zam-597] > write log failed (-5) > > reiser4 panicked cowardly: reiser4[pdflush(6748)]: commit_current_atom > (fs/reiser4/txnmgr.c:1130)[zam-597] > write log failed (-5) > > and the machine is *frozen* > > the harddisk is encrypted via loop-aes v3.1c (loop4). i think it's a > reiser4 or kernel 2.6.15 bug, because loop-aes with kernel <2.6.15 is > running quite perfekt. fsck.reiser4 1.0.5 says the filesystem is clear. > can you reproduce the problem? > Best Regards, > Patrick > > "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" www.klarmobil.de/index.html?pid=73025 weitergeleitete Nachricht Ende "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" www.klarmobil.de/index.html?pid=73025
Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
Clay Barnes wrote: > To amplify what Hans (accurately) wrote, once you see bad sectors, > that means that you already have many more than you see, and that your > hard drive is all out of spare sectors to silently swap out for when > it finds one. > > Basically, there's so much wrong with the surface that your hard drive > can't hide any more flaws, and has given up trying. > > Hans is right: If you see a single bad sector, the drive is > considered unsafe and trash for even the tightest owner. I don't believe that's quite true. It's my understanding that a drive may have a correctable read error. The data may be too damaged to read from that sector, but rewriting the sector can repair it or remap it to a new undamaged area. The drive cannot make up the lost data though, so it must report the error. The damage can come from a partial write during power down or from data that was marginal to start with and hadn't been read in a long time (Drives will remap sectors even on successful reads, when they have to use too much error correction to get the data, but don't generally do full surface sweeps to check. SMART can be told to do full surface checks, however.) Don't take the existence of a single bad sector as proof that the drive is trash. Instead, check the SMART status and look at the remap rates and error rates. SMART should have a nice summary for you too, either OK, FAILING or FAILED (or similar phrases).
Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
[EMAIL PROTECTED] wrote: > > >Hi, >I don't think that this is an error of the Disc, because I have a brand new >Harddisk (2 day's old). > >greets > > I've had new drives fail immediately. It's almost certainly not cost-effective to fully test each drive before it leaves the factory, so sometimes bad ones do make it through. I had a series of WD drives a few years ago all fail within miserably within a few days to a week, for instance. If you're seeing I/O errors on a brand new drive, it's worth the effort to try to have it exchanged with a different unit at the place where you bought it. Chet
Re: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
Hi, I don't think that this is an error of the Disc, because I have a brand new Harddisk (2 day's old). greets - original Nachricht Betreff: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic Gesendet: Di 31 Jan 2006 04:18:49 CET Von: "Clay Barnes"<[EMAIL PROTECTED]> > To amplify what Hans (accurately) wrote, once you see bad sectors, that > means that you already have many more than you see, and that your hard > drive is all out of spare sectors to silently swap out for when it finds > one. > > Basically, there's so much wrong with the surface that your hard drive > can't hide any more flaws, and has given up trying. > > Hans is right: If you see a single bad sector, the drive is considered > unsafe and trash for even the tightest owner. > > --Clay > > Hans Reiser wrote: > > Wow, are we at last actually stable enough that hardware errors are more > > of a problem than software errors for our Reiser4 users? > > > > Rudekjan, you have a bad sector, buy a new drive, use dd_rescue to copy > > to it, don't run reiser4.fsck until you get the data onto the new > > drive. Why buy a new drive? Because after the first user visible bad > > sector, your odds of more bad sectors over time go WAY up. Your > > time+data are too valuable. > > > > Hans > > > > [EMAIL PROTECTED] wrote: > > > > > >> i'm again... here are some more informations. i haven't encrypted my data > and the error above the reiser4 panic is: > >> > >> end_request: I/O error, dev sdb, sector 64412 > >> > >> hope thats help finding the bug > >> > >> greets > >> > >> Jan > >> > >> - weitergeleitete Nachricht - > >> > >> > >> Subject: Re: 2.6.15.1+reiser4 Kernel Panic > >> Date: Di 31 Jan 2006 01:49:38 CET > >> From: [EMAIL PROTECTED] > >> > >> > >> > >> > >>> Hi, > >>> i have the same Problem witch 2.6.16-rc1 with the reiser4 Patch from > >>> ftp.namesys.com. > >>> Same error and the System is frozen to. But I wanted to copy data from > >>> Partition A (Reiser3) to Partition B (Reiser4). > >>> > >>> greets > >>> > >>> Jan > >>> > >>> From: "Vladimir V. Saveliev" <[EMAIL PROTECTED]> > >>>To: Ps <[EMAIL PROTECTED]> > >>>Date: Mon, 30 Jan 2006 11:29:18 +0300 > >>>Subject: Re: 2.6.15.1+reiser4 Kernel Panic > >>>Hello > >>> > >>>On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: > >>>> Hi, > >>>> > >>>> i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch > from > >>>> ftp.namesys.com, when writing data to a usb harddisk. > >>>> > >>>> kernel output: > >>>> loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > >>>> reiser4 panicked cowardly: reiser4[pdflush(6748)]: > >>> commit_current_atom > >>>> (fs/reiser4/txnmgr.c:1130)[zam-597] > >>>> write log failed (-5) > >>>> > >>>> reiser4 panicked cowardly: reiser4[pdflush(6748)]: > >>> commit_current_atom > >>>> (fs/reiser4/txnmgr.c:1130)[zam-597] > >>>> write log failed (-5) > >>>> > >>>> and the machine is *frozen* > >>>> > >>>> the harddisk is encrypted via loop-aes v3.1c (loop4). i think > it's > >>> a > >>>> reiser4 or kernel 2.6.15 bug, because loop-aes with kernel > <2.6.15 > >>> is > >>>> running quite perfekt. fsck.reiser4 1.0.5 says the filesystem > is > >>> clear. > >>>> > >>> > >>>can you reproduce the problem? > >>> > >>>> Best Regards, > >>>> Patrick > >>>> > >>>> > >>> > >>> > >>> > >>> > >>> "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" > >>> www.klarmobil.de/index.html?pid=73025 > >>> > >>> > >>> > >>> > >>> > >> > >> weitergeleitete Nachricht Ende > >> > >> > >> > >> > >> "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" > >> www.klarmobil.de/index.html?pid=73025 > >> > >> > >> > >> > >> > >> > > > > > > > > --- original Nachricht Ende "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" www.klarmobil.de/index.html?pid=73025
Re: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
Hi all, I've had brand new drives fail the moment power was applied - sometimes even the best just get a bad drive through. You could try using smartmontools to non-destructively find out what the drive thinks of itself - a blog entry describing one person's adventures with these tools is here: http://scottstuff.net/blog/articles/tag/drive Good luck, I hope this gives you some useful information. David Quoting [EMAIL PROTECTED]: > > > Hi, > I don't think that this is an error of the Disc, because I have a brand new > Harddisk (2 day's old). > > greets > - original Nachricht ---- > > Betreff: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic > Gesendet: Di 31 Jan 2006 04:18:49 CET > Von: "Clay Barnes"<[EMAIL PROTECTED]> > > > To amplify what Hans (accurately) wrote, once you see bad sectors, that > > means that you already have many more than you see, and that your hard > > drive is all out of spare sectors to silently swap out for when it finds > > one. > > > > Basically, there's so much wrong with the surface that your hard drive > > can't hide any more flaws, and has given up trying. > > > > Hans is right: If you see a single bad sector, the drive is considered > > unsafe and trash for even the tightest owner. > > > > --Clay > > > > Hans Reiser wrote: > > > Wow, are we at last actually stable enough that hardware errors are more > > > of a problem than software errors for our Reiser4 users? > > > > > > Rudekjan, you have a bad sector, buy a new drive, use dd_rescue to copy > > > to it, don't run reiser4.fsck until you get the data onto the new > > > drive. Why buy a new drive? Because after the first user visible bad > > > sector, your odds of more bad sectors over time go WAY up. Your > > > time+data are too valuable. > > > > > > Hans > > > > > > [EMAIL PROTECTED] wrote: > > > > > > > > >> i'm again... here are some more informations. i haven't encrypted my > data > > and the error above the reiser4 panic is: > > >> > > >> end_request: I/O error, dev sdb, sector 64412 > > >> > > >> hope thats help finding the bug > > >> > > >> greets > > >> > > >> Jan > > >> > > >> - weitergeleitete Nachricht - > > >> > > >> > > >> Subject: Re: 2.6.15.1+reiser4 Kernel Panic > > >> Date: Di 31 Jan 2006 01:49:38 CET > > >> From: [EMAIL PROTECTED] > > >> > > >> > > >> > > >> > > >>> Hi, > > >>> i have the same Problem witch 2.6.16-rc1 with the reiser4 Patch from > > >>> ftp.namesys.com. > > >>> Same error and the System is frozen to. But I wanted to copy data from > > >>> Partition A (Reiser3) to Partition B (Reiser4). > > >>> > > >>> greets > > >>> > > >>> Jan > > >>> > > >>> From: "Vladimir V. Saveliev" <[EMAIL PROTECTED]> > > >>>To: Ps <[EMAIL PROTECTED]> > > >>>Date: Mon, 30 Jan 2006 11:29:18 +0300 > > >>>Subject: Re: 2.6.15.1+reiser4 Kernel Panic > > >>>Hello > > >>> > > >>>On Sun, 2006-01-29 at 11:44 +0100, Ps wrote: > > >>>> Hi, > > >>>> > > >>>> i've got a kernel panic with kernel 2.6.15.1 + reiser4 patch > > from > > >>>> ftp.namesys.com, when writing data to a usb harddisk. > > >>>> > > >>>> kernel output: > > >>>> loop4: loop_end_io_transfer err=-95 bi_rw=0x5 > > >>>> reiser4 panicked cowardly: reiser4[pdflush(6748)]: > > >>> commit_current_atom > > >>>> (fs/reiser4/txnmgr.c:1130)[zam-597] > > >>>> write log failed (-5) > > >>>> > > >>>> reiser4 panicked cowardly: reiser4[pdflush(6748)]: > > >>> commit_current_atom > > >>>> (fs/reiser4/txnmgr.c:1130)[zam-597] > > >>>> write log failed (-5) > > >>>> > > >>>> and the machine is *frozen* > > >>>> > > >>>> the harddisk is encrypted via loop-aes v3.1c (loop4). i think > > it's > > >>> a > > >>>> reiser4 or kernel 2.6.15 bug, because loop-aes with kernel > > <2.6.15 > > >>> is > > >>>> running quite perfekt. fsck.reiser4 1.0.5 says the filesystem > > is > > >>> clear. > > >>>> > > >>> > > >>>can you reproduce the problem? > > >>> > > >>>> Best Regards, > > >>>> Patrick > > >>>> > > >>>> > > >>> > > >>> > > >>> > > >>> > > >>> "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" > > >>> www.klarmobil.de/index.html?pid=73025 > > >>> > > >>> > > >>> > > >>> > > >>> > > >> > > >> weitergeleitete Nachricht Ende > > >> > > >> > > >> > > >> > > >> "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" > > >> www.klarmobil.de/index.html?pid=73025 > > >> > > >> > > >> > > >> > > >> > > >> > > > > > > > > > > > > > > > --- original Nachricht Ende > > > > > "Jetzt Handykosten senken mit klarmobil - 14 Ct./Min.! Hier klicken" > www.klarmobil.de/index.html?pid=73025 > > - This mail sent through IMP: http://horde.org/imp/
Re: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
[EMAIL PROTECTED] wrote (ao): > I don't think that this is an error of the Disc, because I have a > brand new Harddisk (2 day's old). I once had four new disks, all DOA, each of them in a different way. And last month nine, out of which two fail to pass 'badblocks'. New disks are always a suspect as they don't have a proven track record yet (pun intended ;-). Kind regards, Sander -- Humilis IT Services and Solutions http://www.humilis.net
Re: Re: Wtr.: Re: 2.6.15.1+reiser4 Kernel Panic
have a look at http://lkml.org/lkml/2006/1/21/79 three people have damaged harddrives??? greets Patrick Am Dienstag, den 31.01.2006, 17:27 +0100 schrieb Sander: > [EMAIL PROTECTED] wrote (ao): > > I don't think that this is an error of the Disc, because I have a > > brand new Harddisk (2 day's old). > > I once had four new disks, all DOA, each of them in a different way. > > And last month nine, out of which two fail to pass 'badblocks'. > > New disks are always a suspect as they don't have a proven track record > yet (pun intended ;-). > > Kind regards, Sander >
