Just a small point, why call grep twice below? - if you are looking for
something like "Filesystem state:error" then use
egrep 'Filesystem state:.*error'
>> with_error=`dumpe2fs -h $DEVICE 2>/dev/null | grep "Filesystem
>> state:" | grep "error"`
>> if [ -n "$with_error" ]; then
On 2/22/2011 8:53 AM, Dejan Muhamedagic wrote:
> Hi Bernd,
>
> On Tue, Feb 22, 2011 at 12:49:00AM +0100, Bernd Schubert wrote:
>> Hello Dejan,
...
>> And of course, no filesystem is free of bugs. Which is why until now
>> extX suggests frequent fscks.
>
> Hmpf. OK, must say that I expected it to
Hi Bernd,
On Tue, Feb 22, 2011 at 12:49:00AM +0100, Bernd Schubert wrote:
> Hello Dejan,
>
>
> On 02/21/2011 05:43 PM, Dejan Muhamedagic wrote:
> >
> > No. ext3 is a filesystem with a journal, so it is considered
> > that it can recover without fsck. Otherwise, there's a parameter
> > called ru
Hello Dejan,
On 02/21/2011 05:43 PM, Dejan Muhamedagic wrote:
>
> No. ext3 is a filesystem with a journal, so it is considered
> that it can recover without fsck. Otherwise, there's a parameter
> called run_fsck, check the meta data: crm ra info Filesystem.
>
no, not if it writes "Warning: mou
Hi,
On Fri, Feb 18, 2011 at 11:56:49AM -0500, Tony Nelson wrote:
> Hi All,
>
> I have a small cluster configured like this:
>
> [-- config -]
> root@ihdb2:~# crm configure show
> node $id="3888bf0f-3e06-4ad8-a2c2-297451128d3d" ihdb1
> node $id="a1f70384-6684-47e6-ba00
Hi All,
I have a small cluster configured like this:
[-- config -]
root@ihdb2:~# crm configure show
node $id="3888bf0f-3e06-4ad8-a2c2-297451128d3d" ihdb1
node $id="a1f70384-6684-47e6-ba00-ed082dee7a56" ihdb2
primitive bacula-fd lsb:bacula-fd.local \
meta target
