Re: Reiser4 for 2.6.36 kernel panic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Yeah, well all I wanted to report that it hadn't become read-only in
last 17 days :D

When I said it's fine, maybe I should have clarified it :D

On Fri, Mar 25, 2011 at 2:48 AM, Edward Shishkin
<edward.shishkin@xxxxxxxxx> wrote:
> 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@xxxxxxxxx>
>> Â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
>>>
>
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux File System Development]     [Linux BTRFS]     [Linux NFS]     [Linux Filesystems]     [Ext4 Filesystem]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Resources]

  Powered by Linux