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

Re: files in /etc/xinetd.d become 0 byte size

To: "Eric Sandeen" <sandeen@sgi.com>
Subject: Re: files in /etc/xinetd.d become 0 byte size
From: "Chris Pascoe" <c.pascoe@itee.uq.edu.au>
Date: Wed, 27 Mar 2002 18:26:54 +1000
Cc: "linux-xfs" <linux-xfs@oss.sgi.com>
References: <3C961055.FF5DF9C6@ch.sauter-bc.com> <1017176697.16815.21.camel@stantz.corp.sgi.com> <3CA0E904.1080907@koschikode.com> <1017179446.17163.29.camel@stantz.corp.sgi.com> <3CA177A1.DA2AD64F@ch.sauter-bc.com>
Sender: owner-linux-xfs@oss.sgi.com

Simon Matter writes:

> The culprit was the remount readonly feature of XFS enabled kernels
> which was buggy. It does not apply to ext2/3 filesystems.
>
> The bug is fixed in current CVS as well as in the upcoming 2.4.9-31
> based XFS 1.1 release.

Hi Eric,

I was wondering if this the same thing that was causing inconsistent
snapshots (remember the directories that wouldn't show in ls - back after
the change to speedup xfs_freeze), and thus if it is now solved?

Thanks,
Chris

Follow-Ups:
- Re: files in /etc/xinetd.d become 0 byte size
  - From: Eric Sandeen <sandeen@sgi.com>

References:
- files in /etc/xinetd.d become 0 byte size
  - From: Simon Matter <simon.matter@ch.sauter-bc.com>
- Re: files in /etc/xinetd.d become 0 byte size
  - From: Florin Andrei <florin@sgi.com>
- Re: files in /etc/xinetd.d become 0 byte size
  - From: Juri Haberland <juri@koschikode.com>
- Re: files in /etc/xinetd.d become 0 byte size
  - From: Florin Andrei <florin@sgi.com>
- Re: files in /etc/xinetd.d become 0 byte size
  - From: Simon Matter <simon.matter@ch.sauter-bc.com>

Prev by Date: 1.1PR2 LVM warning, sunit/swidth query
Next by Date: Can't build CVS kernels of 20020321 & 20020327
Previous by thread: Re: files in /etc/xinetd.d become 0 byte size
Next by thread: Re: files in /etc/xinetd.d become 0 byte size
Index(es):
- Date
- Thread