On 04/20/2010 08:25 AM, Tim Serong wrote:
> I think you really need to determine with certainty exactly what it is that's
> holding what file(s) open. Unfortunately, aside from the "fuser" command to
> see what processes are accessing a given filesystem, I'm not sure what else
> to suggest at this
On 4/20/2010 at 03:36 PM, luben karavelov wrote:
> >> My understanding is
> >> that nfsd is a kernel thread. In fact this is the case here:
> >>
> >> r...@lab2:~# ps axu | grep nfs
> >>
> >> root 913 0.0 0.0356 144 pts/2R+ 19:01 0:00 grep nfs
> >> root 25379 0.0
On 04/19/2010 09:29 PM, Lars Marowsky-Bree wrote:
> On 2010-04-19T14:05:48, Florian Haas wrote:
>
>> - EvmsSCC and
>> - Evmsd (both apply to EVMS, which is no longer maintained);
>>
>> - LinuxSCSI (superseded by SCSI reservations and SF-EX);
>>
>> - drbd (superseded by ocf:linbit:drbd);
>>
>> - p
On 04/20/2010 07:03 AM, Tim Serong wrote:
> On 4/20/2010 at 06:48 AM, Lars Marowsky-Bree wrote:
>> In general, I think the ability to depreciate functionality is needed,
>> but shouldn't be slip-streamed into a minor dot release, and we first
>> need to do some more home work to get our infrast
On 15.04.2010 05:01, Tim Serong wrote:
> On 4/15/2010 at 02:06 AM, luben karavelov wrote:
>
>> On 14.04.2010 08:59, Tim Serong wrote:
>>
>>> Can you be more specific about that? From memory it should just be nfsd
>>> processes that have the open file handles.
>>>
>>> What happens if you
On 4/20/2010 at 06:48 AM, Lars Marowsky-Bree wrote:
> On 2010-04-19T22:22:41, Lars Ellenberg wrote:
>
> > > - EvmsSCC and
> > > - Evmsd (both apply to EVMS, which is no longer maintained);
> > Fine with me, as newer distributions don't ship with EVMS anymore anyways.
> > Older distros (rea
On Mon, Apr 19, 2010 at 10:48:48PM +0200, Lars Marowsky-Bree wrote:
> On 2010-04-19T22:22:41, Lars Ellenberg wrote:
>
> > > - EvmsSCC and
> > > - Evmsd (both apply to EVMS, which is no longer maintained);
> > Fine with me, as newer distributions don't ship with EVMS anymore anyways.
> > Older dis
On 2010-04-19T22:22:41, Lars Ellenberg wrote:
> > - EvmsSCC and
> > - Evmsd (both apply to EVMS, which is no longer maintained);
> Fine with me, as newer distributions don't ship with EVMS anymore anyways.
> Older distros (read: sles10) can easily keep the latest copy of those.
Ah, damn ;-) I'd
On Mon, Apr 19, 2010 at 02:05:48PM +0200, Florian Haas wrote:
> Hello,
>
> in case you haven't yet noticed: as of resource-agents 1.0.2, several
> Linux-HA resource agents are marked as deprecated:
>
> - EvmsSCC and
> - Evmsd (both apply to EVMS, which is no longer maintained);
Fine with me, as
On 2010-04-19T14:05:48, Florian Haas wrote:
> - EvmsSCC and
> - Evmsd (both apply to EVMS, which is no longer maintained);
>
> - LinuxSCSI (superseded by SCSI reservations and SF-EX);
>
> - drbd (superseded by ocf:linbit:drbd);
>
> - pingd (superseded by ocf:pacemaker:pingd, which in turn is n
Hello,
After last week's resource-agents 1.0.3 release, I have merged the
exportfs resource agent, which has lived in its separate branch so far,
into the default branch.
exportfs was thankfully submitted by Ben Timby, and manages NFS exports
on a per-directory basis, without ever killing nfsd. T
On Mon, Apr 19, 2010 at 2:05 PM, Florian Haas wrote:
> Hello,
>
> in case you haven't yet noticed: as of resource-agents 1.0.2, several
> Linux-HA resource agents are marked as deprecated:
>
> - EvmsSCC and
> - Evmsd (both apply to EVMS, which is no longer maintained);
>
> - LinuxSCSI (superseded
Hello,
in case you haven't yet noticed: as of resource-agents 1.0.2, several
Linux-HA resource agents are marked as deprecated:
- EvmsSCC and
- Evmsd (both apply to EVMS, which is no longer maintained);
- LinuxSCSI (superseded by SCSI reservations and SF-EX);
- drbd (superseded by ocf:linbit:dr
On 04/19/2010 01:33 PM, Florian Haas wrote:
> Yes it does. VMware Server 2 only works with .vmdk images as far as I'm
> informed, and can't use raw block devices.
Correct
--
Cristian Mammoli
APRA SISTEMI srl
Via Brodolini,6 Jesi (AN)
tel dir. 0731 719822
Web www.apra.it
e-mail c.mamm...@apra
On 2010-04-19 13:24, Dejan Muhamedagic wrote:
That should be a job for the Filesystem resource agent, you should raise
timeouts there imho... Anyway it doesn't hurt at all. Ask Florian to add
your patch in the next release.
>>> No, that is indeed a job for the Filesystem RA.
>
> T
On Mon, Apr 19, 2010 at 01:24:05PM +0200, Lars Marowsky-Bree wrote:
> On 2010-04-17T21:04:06, Lars Ellenberg wrote:
>
> > This is the interdiff:
> >
> > Bump the so version, note this is the libtool
> > "interface:revision:age" way, the resulting soname
> > is libplumb.so.2.1.0
> >
> > --- a/li
On 2010-04-17T21:04:06, Lars Ellenberg wrote:
> This is the interdiff:
>
> Bump the so version, note this is the libtool
> "interface:revision:age" way, the resulting soname
> is libplumb.so.2.1.0
>
> --- a/lib/clplumbing/Makefile.am Thu Apr 15 15:58:50 2010 +0200
> +++ b/lib/clplumbing/Ma
Hi,
On Mon, Apr 19, 2010 at 12:44:20PM +0200, Lars Ellenberg wrote:
> On Mon, Apr 19, 2010 at 11:07:31AM +0200, Florian Haas wrote:
> > On 2010-04-19 11:02, Cristian Mammoli - Apra Sistemi wrote:
> > > On 04/16/2010 08:56 AM, Marko Potocnik wrote:
> > >> Hi,
> > >>
> > >> we're also using vmware r
On Mon, Apr 19, 2010 at 11:07:31AM +0200, Florian Haas wrote:
> On 2010-04-19 11:02, Cristian Mammoli - Apra Sistemi wrote:
> > On 04/16/2010 08:56 AM, Marko Potocnik wrote:
> >> Hi,
> >>
> >> we're also using vmware resource agent at out company and we found
> >> problems with stopping virtual mac
Hi,
We test VirtualDomain on Xen.(at RHEL5.5)
But, a problem is taking place when stop processing is carried out somehow or
other.
VirtualDomain_Status carried out by stop processing returns "no state" at
considerably high frequency.
For this problem, it is worked to destroy the guest(VM).
W
On 2010-04-19 11:02, Cristian Mammoli - Apra Sistemi wrote:
> On 04/16/2010 08:56 AM, Marko Potocnik wrote:
>> Hi,
>>
>> we're also using vmware resource agent at out company and we found
>> problems with stopping virtual machines and unmounting underlaying
>> filesystem right afterwards. Filesyste
On 04/16/2010 08:56 AM, Marko Potocnik wrote:
> Hi,
>
> we're also using vmware resource agent at out company and we found
> problems with stopping virtual machines and unmounting underlaying
> filesystem right afterwards. Filesystem was still in use and umount failed.
> Solution was to call "sync"
22 matches
Mail list logo
