"[email protected]" <[email protected]> wrote:
Send rhelv5-list mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://www.redhat.com/mailman/listinfo/rhelv5-list
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of rhelv5-list digest..."
Today's Topics:
1. Sometimes, ext4 fs fall into readd only state. (Kirby Zhou)
2. Re: Sometimes, ext4 fs fall into readd only state.
(Benjamin Franz)
3. Re: Sometimes, ext4 fs fall into readd only state.
(Eugene Vilensky)
4. Re: Puppet or cfengine? (Darren Patterson)
5. Re: Sometimes, ext4 fs fall into readd only state. (nodata)
6. Re: Sometimes, ext4 fs fall into readd only state.
(Matthew J. Salerno)
7. Re: Sometimes, ext4 fs fall into readd only state.
(Matthew J. Salerno)
----------------------------------------------------------------------
Message: 1
Date: Wed, 18 Aug 2010 00:14:41 +0800
From: "Kirby Zhou" <[email protected]>
To: "'Red Hat Enterprise Linux 5 \(Tikanga\) discussion mailing-list'"
<[email protected]>
Subject: [rhelv5-list] Sometimes, ext4 fs fall into readd only state.
Message-ID: <000601cb3e27$4c463fb0$e4d2bf...@com>
Content-Type: text/plain; charset="us-ascii"
Sometimes, ext4 fs fall into readd only state.
It happens randomly.
What can I do for collecting something to report a bug?
Regards
Kirby Zhou
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://www.redhat.com/archives/rhelv5-list/attachments/20100818/23ab9467/attachment.html>
------------------------------
Message: 2
Date: Tue, 17 Aug 2010 09:56:28 -0700
From: Benjamin Franz <[email protected]>
To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list"
<[email protected]>
Subject: Re: [rhelv5-list] Sometimes, ext4 fs fall into readd only
state.
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 08/17/2010 09:14 AM, Kirby Zhou wrote:
>
> Sometimes, ext4 fs fall into readd only state.
>
> It happens randomly.
>
> What can I do for collecting something to report a bug?
>
>
Check your logs (/var/log/messages in particular) to find out *why* it
switched to read-only. Switching to read-only is usually a symptom of a
disk failure. If your /var/log directory is on the affected parition,
configure syslog to remote log to another machine.
--
Benjamin Franz
--
Benjamin Franz
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://www.redhat.com/archives/rhelv5-list/attachments/20100817/518fcecb/attachment.html>
------------------------------
Message: 3
Date: Tue, 17 Aug 2010 12:35:43 -0500
From: Eugene Vilensky <[email protected]>
To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list"
<[email protected]>
Subject: Re: [rhelv5-list] Sometimes, ext4 fs fall into readd only
state.
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Aug 17, 2010 at 11:56 AM, Benjamin Franz <[email protected]> wrote:
> On 08/17/2010 09:14 AM, Kirby Zhou wrote:
>
> Sometimes, ext4 fs fall into readd only state.
>
> It happens randomly.
>
> What can I do for collecting something to report a bug?
>
>
>
>
>
> Check your logs (/var/log/messages in particular) to find out *why* it
> switched to read-only. Switching to read-only? is usually a symptom of a
> disk failure.? If your /var/log directory is on the affected parition,
> configure syslog to remote log to another machine.
in our environment, this was almost always caused by virtual machine
disk timeout setting being too low for peak storage latencies...
------------------------------
Message: 4
Date: Tue, 17 Aug 2010 11:52:30 -0700
From: Darren Patterson <[email protected]>
To: "Red Hat Enterprise Linux 5 \(Tikanga\) discussion mailing-list"
<[email protected]>
Subject: Re: [rhelv5-list] Puppet or cfengine?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Aug 11, 2010, at 11:33 AM, Troels Arvin wrote:
> Darren Patterson wrote:
>> We use puppet extensively here at Stanford (central IT Services) - to my
>> knowledge, we are the largest puppet user at the moment. I can highly
>> recommend puppet above cfengine.
>
> Thanks to Derek and Darren.
>
> About your cfengine experiences: Have you tried the latest cfengine
> generation (3), or were your experiences with cfengine 2?
My experience was with cfengine 2.
-darren
------------------------------
Message: 5
Date: Tue, 17 Aug 2010 23:54:23 +0200
From: nodata <[email protected]>
To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list"
<[email protected]>
Subject: Re: [rhelv5-list] Sometimes, ext4 fs fall into readd only
state.
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
On 17/08/10 18:56, Benjamin Franz wrote:
> On 08/17/2010 09:14 AM, Kirby Zhou wrote:
>>
>> Sometimes, ext4 fs fall into readd only state.
>>
>> It happens randomly.
>>
>> What can I do for collecting something to report a bug?
>>
>>
>
> Check your logs (/var/log/messages in particular) to find out *why* it
> switched to read-only. Switching to read-only is usually a symptom of a
> disk failure. If your /var/log directory is on the affected parition,
> configure syslog to remote log to another machine.
Or look at dmesg.
>
> --
> Benjamin Franz
>
> --
> Benjamin Franz
>
>
>
> _______________________________________________
> rhelv5-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhelv5-list
------------------------------
Message: 6
Date: Tue, 17 Aug 2010 18:51:48 -0400
From: "Matthew J. Salerno" <[email protected]>
To: "Red Hat Enterprise Linux 5 \(Tikanga\) discussion mailing-list"
<[email protected]>, "Red Hat Enterprise Linux 5 \(Tikanga\)
discussion mailing-list" <[email protected]>
Subject: Re: [rhelv5-list] Sometimes, ext4 fs fall into readd only
state.
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Check dmesg. Also increase the logging on smartd. Could be your disk going
bad, a flakey controller, flakey disk cable or flakey controller driver. Ext4
usually goes read-only for self preservation.
"nodata" <[email protected]> wrote:
>On 17/08/10 18:56, Benjamin Franz wrote:
>> On 08/17/2010 09:14 AM, Kirby Zhou wrote:
>>>
>>> Sometimes, ext4 fs fall into readd only state.
>>>
>>> It happens randomly.
>>>
>>> What can I do for collecting something to report a bug?
>>>
>>>
>>
>> Check your logs (/var/log/messages in particular) to find out *why* it
>> switched to read-only. Switching to read-only is usually a symptom of a
>> disk failure. If your /var/log directory is on the affected parition,
>> configure syslog to remote log to another machine.
>
>Or look at dmesg.
>
>>
>> --
>> Benjamin Franz
>>
>> --
>> Benjamin Franz
>>
>>
>>
>> _______________________________________________
>> rhelv5-list mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/rhelv5-list
>
>_______________________________________________
>rhelv5-list mailing list
>[email protected]
>https://www.redhat.com/mailman/listinfo/rhelv5-list
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------------------------------
Message: 7
Date: Tue, 17 Aug 2010 18:51:48 -0400
From: "Matthew J. Salerno" <[email protected]>
To: "Red Hat Enterprise Linux 5 \(Tikanga\) discussion mailing-list"
<[email protected]>, "Red Hat Enterprise Linux 5 \(Tikanga\)
discussion mailing-list" <[email protected]>
Subject: Re: [rhelv5-list] Sometimes, ext4 fs fall into readd only
state.
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Check dmesg. Also increase the logging on smartd. Could be your disk going
bad, a flakey controller, flakey disk cable or flakey controller driver. Ext4
usually goes read-only for self preservation.
"nodata" <[email protected]> wrote:
>On 17/08/10 18:56, Benjamin Franz wrote:
>> On 08/17/2010 09:14 AM, Kirby Zhou wrote:
>>>
>>> Sometimes, ext4 fs fall into readd only state.
>>>
>>> It happens randomly.
>>>
>>> What can I do for collecting something to report a bug?
>>>
>>>
>>
>> Check your logs (/var/log/messages in particular) to find out *why* it
>> switched to read-only. Switching to read-only is usually a symptom of a
>> disk failure. If your /var/log directory is on the affected parition,
>> configure syslog to remote log to another machine.
>
>Or look at dmesg.
>
>>
>> --
>> Benjamin Franz
>>
>> --
>> Benjamin Franz
>>
>>
>>
>> _______________________________________________
>> rhelv5-list mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/rhelv5-list
>
>_______________________________________________
>rhelv5-list mailing list
>[email protected]
>https://www.redhat.com/mailman/listinfo/rhelv5-list
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------------------------------
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
End of rhelv5-list Digest, Vol 42, Issue 23
*******************************************
*********************************************************
THIS ELECTRONIC MAIL MESSAGE AND ANY ATTACHMENT IS
CONFIDENTIAL AND MAY CONTAIN LEGALLY PRIVILEGED
INFORMATION INTENDED ONLY FOR THE USE OF THE INDIVIDUAL
OR INDIVIDUALS NAMED ABOVE.
If the reader is not the intended recipient, or the
employee or agent responsible to deliver it to the
intended recipient, you are hereby notified that any
dissemination, distribution or copying of this
communication is strictly prohibited. If you have
received this communication in error, please reply to the
sender to notify us of the error and delete the original
message. Thank You.
*********************************************************
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
