On Wed, Apr 02, 2008 at 10:25:48AM +0200, Ingeborg Hellemo wrote:
>
> [EMAIL PROTECTED] said:
> > Did you have any recent crashes, panics, or anything that could (even
> > remotely) cause filesystem inconsistencies?
>
> No, that was why I was asking in the first place. The system was freshly
>
[EMAIL PROTECTED] said:
> Did you have any recent crashes, panics, or anything that could (even
> remotely) cause filesystem inconsistencies?
No, that was why I was asking in the first place. The system was freshly
installed from 7.0-RELEASE-amd64-disc1.iso with no error messages during the
in
On Wed, Apr 02, 2008 at 10:12:30AM +0200, Ingeborg Hellemo wrote:
> ~/#fsck /dev/da0s1d
> ** /dev/da0s1d (NO WRITE)
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 -
On Wed, Apr 2, 2008 at 12:54 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 02, 2008 at 09:17:03AM +0200, Ingeborg Hellemo wrote:
> >
> > [EMAIL PROTECTED] said:
> > > > It is possible to have files that are open and held by processes on
> > > > the filesystem that are no longer l
[EMAIL PROTECTED] said:
> > Ingeborg Hellemo wrote:
> > ProLiant DL380 G5, freshly installed FreeBSD 7.0-RELEASE amd64. I have done
> > similar installations on 2 other servers, and suddenly:
> > Any ideas?
>
> fsck -B /var
Good idea!
~/#fsck /dev/da0s1d
** /dev/da0s1d (NO WRITE)
** Last Moun
On Wed, Apr 02, 2008 at 09:17:03AM +0200, Ingeborg Hellemo wrote:
>
> [EMAIL PROTECTED] said:
> > > It is possible to have files that are open and held by processes on
> > > the filesystem that are no longer listed. If you kill the offending
> L > process the space will be freed up.
> >
> > "lsof
Ingeborg Hellemo wrote:
ProLiant DL380 G5, freshly installed FreeBSD 7.0-RELEASE amd64. I have done
similar installations on 2 other servers, and suddenly:
Any ideas?
fsck -B /var
--
Sphinx of black quartz judge my vow.
___
freebsd-stable@freebsd
On Wed, Apr 02, 2008 at 07:41:16PM +1300, Jonathan Chen wrote:
> > > 2) Files which are open (have active file descriptors associated with
> > > them)
> > > on /var before it filled may be causing this. fstat may help you here.
> > But /var is not full. It is _more_ than empty.
> > It is possib
[EMAIL PROTECTED] said:
> What you have might be some corrupted filesystem, but someone more familiar
> with UFS/FFS will have to comment. Output from ffsinfo(8) on that filesystem
> may be useful.
Any wishes for the '-l ' flag? The default gives me a 400Mb file.
--Ingeborg
--
Ingeborg Ă˜strem
[EMAIL PROTECTED] said:
> > It is possible to have files that are open and held by processes on
> > the filesystem that are no longer listed. If you kill the offending
L > process the space will be freed up.
>
> "lsof +aL1 " shows unlinked open files on the specified file
> system (quoting its ma
On Wed, Apr 02, 2008 at 08:03:09AM +0200, Ingeborg Hellemo wrote:
> [EMAIL PROTECTED] said:
> > 2) Files which are open (have active file descriptors associated with them)
> > on /var before it filled may be causing this. fstat may help you here.
>
> But /var is not full. It is _more_ than empty
On Wed, Apr 02, 2008 at 08:03:09AM +0200, Ingeborg Hellemo wrote:
>
> [EMAIL PROTECTED] said:
> > 1) Softupdates can cause this. Run "sync" a few times, then wait 30 seconds
> > or so; does it go away?
>
> Tried. And booted several times. No luck
>
>
> [EMAIL PROTECTED] said:
> > 2) Files whic
[EMAIL PROTECTED] said:
> 1) Softupdates can cause this. Run "sync" a few times, then wait 30 seconds
> or so; does it go away?
Tried. And booted several times. No luck
[EMAIL PROTECTED] said:
> 2) Files which are open (have active file descriptors associated with them)
> on /var before it fil
On Tue, Apr 01, 2008 at 02:57:17PM +0200, Ingeborg Hellemo wrote:
> ProLiant DL380 G5, freshly installed FreeBSD 7.0-RELEASE amd64. I have done
> similar installations on 2 other servers, and suddenly:
>
> ~/#df
> Filesystem1K-blocks UsedAvail Capacity Mounted on
> /d
14 matches
Mail list logo