On Fri, 2006-12-15 at 09:16 -0800, Martin Knoblauch wrote:
> --- Trond Myklebust <[EMAIL PROTECTED]> wrote:
>
> >
> > > Is there a way to find out which files are involved? Nothing
> > seems to
> > > be obviously breaking, but I do not like to get my logfiles filled
> > up.
> >
> > The
--- Trond Myklebust <[EMAIL PROTECTED]> wrote:
>
> > Is there a way to find out which files are involved? Nothing
> seems to
> > be obviously breaking, but I do not like to get my logfiles filled
> up.
>
> The fileid is the same as the inode number. Just convert those
> hexadecimal values
--- Trond Myklebust [EMAIL PROTECTED] wrote:
Is there a way to find out which files are involved? Nothing
seems to
be obviously breaking, but I do not like to get my logfiles filled
up.
The fileid is the same as the inode number. Just convert those
hexadecimal values into ordinary
On Fri, 2006-12-15 at 09:16 -0800, Martin Knoblauch wrote:
--- Trond Myklebust [EMAIL PROTECTED] wrote:
Is there a way to find out which files are involved? Nothing
seems to
be obviously breaking, but I do not like to get my logfiles filled
up.
The fileid is the same as the
--- Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-12-11 at 15:44 -0800, Martin Knoblauch wrote:
> > So far, we are only seeing it on amd-mounted filesystems, not on
> > static NFS mounts. Unfortunatelly, it is difficult to avoid "amd"
> in
> > our environment.
>
> Any chance you
On Mon, 2006-12-11 at 15:44 -0800, Martin Knoblauch wrote:
> So far, we are only seeing it on amd-mounted filesystems, not on
> static NFS mounts. Unfortunatelly, it is difficult to avoid "amd" in
> our environment.
Any chance you could try substituting a recent version of autofs? This
sort of
--- Trond Myklebust <[EMAIL PROTECTED]> wrote:
> On Mon, 2006-12-11 at 08:09 -0800, Martin Knoblauch wrote:
> > Hi, [please CC me, as I am not subscribed]
> >
> > after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel,
> we
> > are seeing repeated occurences of the following
On Mon, 2006-12-11 at 08:09 -0800, Martin Knoblauch wrote:
> Hi, [please CC me, as I am not subscribed]
>
> after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel, we
> are seeing repeated occurences of the following messages (about every
> 45-50 minutes).
>
> It is always the same
Hi, [please CC me, as I am not subscribed]
after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel, we
are seeing repeated occurences of the following messages (about every
45-50 minutes).
It is always the same server (a NetApp filer, mounted via the
user-space automounter "amd") and
Hi, [please CC me, as I am not subscribed]
after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel, we
are seeing repeated occurences of the following messages (about every
45-50 minutes).
It is always the same server (a NetApp filer, mounted via the
user-space automounter amd) and
On Mon, 2006-12-11 at 08:09 -0800, Martin Knoblauch wrote:
Hi, [please CC me, as I am not subscribed]
after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel, we
are seeing repeated occurences of the following messages (about every
45-50 minutes).
It is always the same server
--- Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2006-12-11 at 08:09 -0800, Martin Knoblauch wrote:
Hi, [please CC me, as I am not subscribed]
after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel,
we
are seeing repeated occurences of the following messages (about
On Mon, 2006-12-11 at 15:44 -0800, Martin Knoblauch wrote:
So far, we are only seeing it on amd-mounted filesystems, not on
static NFS mounts. Unfortunatelly, it is difficult to avoid amd in
our environment.
Any chance you could try substituting a recent version of autofs? This
sort of
--- Trond Myklebust [EMAIL PROTECTED] wrote:
On Mon, 2006-12-11 at 15:44 -0800, Martin Knoblauch wrote:
So far, we are only seeing it on amd-mounted filesystems, not on
static NFS mounts. Unfortunatelly, it is difficult to avoid amd
in
our environment.
Any chance you could try
14 matches
Mail list logo
