System: FreeBSD 4.8 with standard config on PII/400...used mainly as a
backup server.
df shows...
Filesystem 1K-blocksUsed Avail Capacity Mounted on
/dev/ad0s1a128990 119660-988 101%/
/dev/ad0s1f257998 4 237356 0%/tmp
/dev/ad0s1g 7426528 2109420
On Mon, Jan 03, 2005 at 04:31:24PM -0600, McCy Ron wrote:
System: FreeBSD 4.8 with standard config on PII/400...used mainly as a
backup server.
df shows...
Filesystem 1K-blocksUsed Avail Capacity Mounted on
/dev/ad0s1a128990 119660-988 101%/
/dev/ad0s1f257998
On Jan 3, 2005, at 4:31 PM, McCy Ron wrote:
System: FreeBSD 4.8 with standard config on PII/400...used mainly as a
backup server.
df shows...
Filesystem 1K-blocksUsed Avail Capacity Mounted on
/dev/ad0s1a128990 119660-988 101%/
/dev/ad0s1f257998 4 237356 0%
--- David Kelly [EMAIL PROTECTED] wrote:
Another goof is for root to write to an unmounted
filesystem. Later
when the filesystem is mounted the written files are
hidden yet still
consume space on the fs containing the mount point
(usually /).
Could you explain how this happens (or point
On Mon, Jan 03, 2005 at 05:07:23PM -0800, Gregor Mosheh wrote:
--- David Kelly [EMAIL PROTECTED] wrote:
Another goof is for root to write to an unmounted
filesystem. Later
when the filesystem is mounted the written files are
hidden yet still
consume space on the fs containing the
On Jan 3, 2005, at 7:07 PM, Gregor Mosheh wrote:
--- David Kelly [EMAIL PROTECTED] wrote:
Another goof is for root to write to an unmounted filesystem.
Later when the filesystem is mounted the written files are hidden
yet still consume space on the fs containing the mount point
(usually /).
Could
