From: Edward Shishkin <edward.shishkin@gmail.com>
To: Dushan Tcholich <dusanc@gmail.com>
Cc: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: Re: Reiser4 for 2.6.36 kernel panic
Date: Fri, 25 Mar 2011 02:48:22 +0100 [thread overview]
Message-ID: <4D8BF466.7080600@gmail.com> (raw)
In-Reply-To: <AANLkTikK8pS_bsxnwYrRd3NVXsR=uf5OWe_2h3+njOVU@mail.gmail.com>
On 03/25/2011 12:15 AM, Dushan Tcholich wrote:
> Btw. I found something suspicious in my /var/log/messages
>
> Mar 24 17:03:48 krshina3 kernel: [18656.820109] ata1: lost interrupt
> (Status 0x50)
> Mar 24 17:03:48 krshina3 kernel: [18656.820128] ata1.00: exception
> Emask 0x10 SAct 0x0 SErr 0x4050002 action 0xe frozen
> Mar 24 17:03:48 krshina3 kernel: [18656.820133] ata1.00: SError: {
> RecovComm PHYRdyChg CommWake DevExch }
> Mar 24 17:03:48 krshina3 kernel: [18656.820137] ata1.00: failed
> command: WRITE DMA
> Mar 24 17:03:48 krshina3 kernel: [18656.820145] ata1.00: cmd
> ca/00:10:18:0e:03/00:00:00:00:00/e1 tag 0 dma 8192 out
> Mar 24 17:03:48 krshina3 kernel: [18656.820146] res
> 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x14 (ATA bus error)
> Mar 24 17:03:48 krshina3 kernel: [18656.820150] ata1.00: status: { DRDY }
> Mar 24 17:03:48 krshina3 kernel: [18656.820161] ata1.00: hard resetting link
> Mar 24 17:03:48 krshina3 kernel: [18657.544072] ata1.01: hard resetting link
> Mar 24 17:03:48 krshina3 kernel: [18658.020149] ata1.00: SATA link up
> 3.0 Gbps (SStatus 123 SControl 300)
> Mar 24 17:03:50 krshina3 kernel: [18658.020161] ata1.01: SATA link
> down (SStatus 4 SControl 300)
> Mar 24 17:03:50 krshina3 kernel: [18658.036242] ata1.00: configured for UDMA/133
> Mar 24 17:03:50 krshina3 kernel: [18658.036248] ata1.00: device
> reported invalid CHS sector 0
> Mar 24 17:03:50 krshina3 kernel: [18658.036257] ata1: EH complete
>
> But it doesn't make kernel panic,
It shouldn't panic with such mount options.
At the "moment of truth" your system will become read-only..
system continues to work 24/7.
>
> Thanks
>
> Dushan
>
> On Fri, Mar 25, 2011 at 12:12 AM, Dushan Tcholich<dusanc@gmail.com> wrote:
>> cat /etc/fstab | grep "#" -v
>>
>>
>> /dev/sda1 /boot ext2 noauto,noatime 1 2
>> /dev/md1 none swap sw 0 0
>> /dev/sda2 / reiser4
>> noatime,onerror=remount-ro 0 0
>> /dev/md126 /mnt/media reiser4
>> noatime,users,onerror=remount-ro 0 0
>> /dev/md127 /usr/portage reiser4
>> noatime,onerror=remount-ro 0 0
>>
>> shm /dev/shm tmpfs
>> nodev,nosuid,noexec 0 0
>>
>> This is fstab for last 2 weeks:D
>>
next prev parent reply other threads:[~2011-03-25 1:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 18:08 Reiser4 for 2.6.36 kernel panic Dushan Tcholich
2011-03-04 18:37 ` Edward Shishkin
2011-03-07 18:50 ` Dushan Tcholich
2011-03-24 22:13 ` Dushan Tcholich
2011-03-24 22:34 ` Edward Shishkin
2011-03-24 23:12 ` Dushan Tcholich
2011-03-24 23:15 ` Dushan Tcholich
2011-03-25 1:48 ` Edward Shishkin [this message]
2011-03-25 7:16 ` Dushan Tcholich
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=4D8BF466.7080600@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=dusanc@gmail.com \
--cc=reiserfs-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.