Re: File System errors

2007-05-16 Thread Gary Kline
On Wed, May 16, 2007 at 06:34:42AM +0100, Matthew Seaman wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256
 
 Gary Kline wrote:
 
  I booted into single-user (press 4) and got rid of tons of junk
  left in /var/tmp.  Then I did a mount -a and and fsck -y.
 
 But not in that order.  fsck -y *first*, then mount -a, then start
 removing files from /var/tmp.
 

Well, my DNS server ran out of space and when I was able to 
bring it back up, only / was mounted.  I was able to rm things
from /var and /tmp to give me some assurance of a regular boot.
Yes, before I did my first set of file unlinks I did fsck -y /;
it was the only thing mounted.  

I'm usually pretty disciplined about / having enough space.  Not
this time... .

gary


   Matthew
 
 - -- 
 Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
   Flat 3
 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
   Kent, CT11 9PW
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.3 (FreeBSD)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
 iD8DBQFGSpfy8Mjk52CukIwRCPsuAJsFQwT+G5APT3a4XccFcmODfYXMlQCfYCQR
 BI5cpzCkfYKOkFfSCGo9HvQ=
 =VlWP
 -END PGP SIGNATURE-

-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-16 Thread Mikhail Goriachev
Ross Penner wrote:
 On 5/15/07, Roland Smith [EMAIL PROTECTED] wrote:
 On Tue, May 15, 2007 at 12:15:06PM -0600, Ross Penner wrote:
  I recently had my system freeze so I had to manually restart it. I was
  worried that there would be some problems with the filesystem so I
  looked into the matter and discovered the utility fsck. I ran this as
  root and I got the following:
 You normally don't have to do this manually. If a filesystem isn't
 cleanly unmounted, it is automatically checked (in the background if
 possible, so it might take a while) on the next boot.

 And in that case fsck won't bother you unless it runs into problems it
 can't solve.

 Roland
 --
 R.F.Smith   http://www.xs4all.nl/~rsmith/
 [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
 pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)

 
 Thanks for everybodies help. I restarted in single user mode which
 allowed me to do the check manually. I'll probably just let the
 background check go if it happens again.


By default, the background checking doesn't do much. In my experience,
every time one of the machines goes down, I have to schedule a manual
fsck (fsck -fy) in single user mode.

Another option, probably, is this:

fsck_y_enable=YES

It sounds scary though.


Regards,
Mikhail.

-- 
Mikhail Goriachev
Webanoide

Telephone: +61 (0)3 62252501
Mobile Phone: +61 (0)4 38255158
E-Mail: [EMAIL PROTECTED]
Web: www.webanoide.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-15 Thread Chuck Swiger

On May 15, 2007, at 11:15 AM, Ross Penner wrote:
[ ... about fsck... ]

It seems to my unexperienced eye that their are problems in some of
the filesystems, but they arn't being resolved. I tried running fsck
-y  and nothing changed. What am I doing wrong? How can I resolve
these issues? Thanks for any help you can offer.


You can only (usefully) run fsck on unmounted filesystems.  Normally,  
if a filesystem has problems and cannot be mounted, the system will  
not enter multi-user mode and will require the operator to run it  
from single-user mode.  You can also boot off of a CD and fsck the  
hard drive that way.


Note that you generally need to answer yes to the repair questions  
fsck asks of you


--
-Chuck

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-15 Thread Jerry McAllister
On Tue, May 15, 2007 at 12:15:06PM -0600, Ross Penner wrote:

 I recently had my system freeze so I had to manually restart it. I was
 worried that there would be some problems with the filesystem so I
 looked into the matter and discovered the utility fsck. I ran this as
 root and I got the following:
 
 rosbot# fsck
 ** /dev/ar0s1a (NO WRITE)
 ** Last Mounted on /
 ** Root file system
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 1549 files, 27349 used, 226466 free (650 frags, 28227 blocks, 0.3%
 fragmentation)
 ** /dev/ar0s1e (NO WRITE)
 ** Last Mounted on /tmp
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 39 files, 2445 used, 251370 free (50 frags, 31415 blocks, 0.0% 
 fragmentation)
 ** /dev/ar0s1f (NO WRITE)
 ** Last Mounted on /usr
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 FREE BLK COUNT(S) WRONG IN SUPERBLK
 SALVAGE? no
 
 292882 files, 98192697 used, 135895442 free (39610 frags, 16981979
 blocks, 0.0% fragmentation)
 ** /dev/ar0s1d (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
 UNREF FILE I=117781  OWNER=root MODE=140666
 SIZE=0 MTIME=May 15 09:56 2007
 CLEAR? no
 
 UNREF FILE I=141337  OWNER=teamspeak MODE=100600
 SIZE=2048 MTIME=May 15 09:56 2007
 CLEAR? no
 
 ** Phase 5 - Check Cyl groups
 FREE BLK COUNT(S) WRONG IN SUPERBLK
 SALVAGE? no
 
 SUMMARY INFORMATION BAD
 SALVAGE? no
 
 18514 files, 70825 used, 905728 free (6688 frags, 112380 blocks, 0.7%
 fragmentation)
 
 
 It seems to my unexperienced eye that their are problems in some of
 the filesystems, but they arn't being resolved. I tried running fsck
 -y  and nothing changed. What am I doing wrong? How can I resolve
 these issues? Thanks for any help you can offer.

I may be mistaking something, but it kind of looks like it doesn't
have write access to the drive.Fsck has to be able to write to
fix anything.

Also, you need to answer 'y' when it asks to 'salvage'.  Of course, 
doing the fsck -y should take care of that issue, but it still must
have write permission.   I don't know why it wouldn't have write ability.

jerry

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-15 Thread Roland Smith
On Tue, May 15, 2007 at 12:15:06PM -0600, Ross Penner wrote:
  I recently had my system freeze so I had to manually restart it. I was
  worried that there would be some problems with the filesystem so I
  looked into the matter and discovered the utility fsck. I ran this as
  root and I got the following:

You normally don't have to do this manually. If a filesystem isn't
cleanly unmounted, it is automatically checked (in the background if
possible, so it might take a while) on the next boot. 

And in that case fsck won't bother you unless it runs into problems it
can't solve.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp15Vco5ZzC4.pgp
Description: PGP signature


Re: File System errors

2007-05-15 Thread Ross Penner

On 5/15/07, Roland Smith [EMAIL PROTECTED] wrote:

On Tue, May 15, 2007 at 12:15:06PM -0600, Ross Penner wrote:
  I recently had my system freeze so I had to manually restart it. I was
  worried that there would be some problems with the filesystem so I
  looked into the matter and discovered the utility fsck. I ran this as
  root and I got the following:

You normally don't have to do this manually. If a filesystem isn't
cleanly unmounted, it is automatically checked (in the background if
possible, so it might take a while) on the next boot.

And in that case fsck won't bother you unless it runs into problems it
can't solve.

Roland
--
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)



Thanks for everybodies help. I restarted in single user mode which
allowed me to do the check manually. I'll probably just let the
background check go if it happens again.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-15 Thread Daniel Molina Wegener

El Mar, 15 de Mayo de 2007, 14:15, Ross Penner escribió:
 I recently had my system freeze so I had to manually restart it. I was
 worried that there would be some problems with the filesystem so I
 looked into the matter and discovered the utility fsck. I ran this as
 root and I got the following:

 rosbot# fsck
 ** /dev/ar0s1a (NO WRITE)
 ** Last Mounted on /
 ** Root file system
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 1549 files, 27349 used, 226466 free (650 frags, 28227 blocks, 0.3%
 fragmentation)
 ** /dev/ar0s1e (NO WRITE)
 ** Last Mounted on /tmp
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 39 files, 2445 used, 251370 free (50 frags, 31415 blocks, 0.0% fragmentation)
 ** /dev/ar0s1f (NO WRITE)
 ** Last Mounted on /usr
 ** Phase 1 - Check Blocks and Sizes
 ** Phase 2 - Check Pathnames
 ** Phase 3 - Check Connectivity
 ** Phase 4 - Check Reference Counts
 ** Phase 5 - Check Cyl groups
 FREE BLK COUNT(S) WRONG IN SUPERBLK
 SALVAGE? no

 292882 files, 98192697 used, 135895442 free (39610 frags, 16981979
 blocks, 0.0% fragmentation)
 ** /dev/ar0s1d (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
 UNREF FILE I=117781  OWNER=root MODE=140666
 SIZE=0 MTIME=May 15 09:56 2007
 CLEAR? no

 UNREF FILE I=141337  OWNER=teamspeak MODE=100600
 SIZE=2048 MTIME=May 15 09:56 2007
 CLEAR? no

 ** Phase 5 - Check Cyl groups
 FREE BLK COUNT(S) WRONG IN SUPERBLK
 SALVAGE? no

 SUMMARY INFORMATION BAD
 SALVAGE? no

 18514 files, 70825 used, 905728 free (6688 frags, 112380 blocks, 0.7%
 fragmentation)


 It seems to my unexperienced eye that their are problems in some of
 the filesystems, but they arn't being resolved. I tried running fsck
 -y  and nothing changed. What am I doing wrong? How can I resolve
 these issues? Thanks for any help you can offer.
 [SNIP]


Hello,

   Try booting in single user mode, then running fsck again with -y parameter --
seems to
need unmounted devices.

Regards,
-- 
 .O. | Daniel Molina Wegener   | C/C++ Developer
 ..O | dmw [at] unete [dot] cl | FOSS Coding Adict
 OOO | BSD  Linux User| Standards Rocks!


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-15 Thread Gary Kline
On Tue, May 15, 2007 at 02:49:59PM -0400, Daniel Molina Wegener wrote:
 
 El Mar, 15 de Mayo de 2007, 14:15, Ross Penner escribió:
  I recently had my system freeze so I had to manually restart it. I was
  worried that there would be some problems with the filesystem so I
  looked into the matter and discovered the utility fsck. I ran this as
  root and I got the following:
 
[[ ...  ]]

 
  ** Phase 5 - Check Cyl groups
  FREE BLK COUNT(S) WRONG IN SUPERBLK
  SALVAGE? no
 
  SUMMARY INFORMATION BAD
  SALVAGE? no
 
  18514 files, 70825 used, 905728 free (6688 frags, 112380 blocks, 0.7%
  fragmentation)
 
 
  It seems to my unexperienced eye that their are problems in some of
  the filesystems, but they arn't being resolved. I tried running fsck
  -y  and nothing changed. What am I doing wrong? How can I resolve
  these issues? Thanks for any help you can offer.
  [SNIP]
 

I ran in to similar snafus with mmy DNS server, very recently.  
I booted into single-user (press 4) and got rid of tons of junk
left in /var/tmp.  Then I did a mount -a and and fsck -y.

If fsck were any more useful, it would be able to cure death!
..Or at least hangovers:-)

goood luck,


gary



-- 
  Gary Kline  [EMAIL PROTECTED]   www.thought.org  Public Service Unix

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: File System errors

2007-05-15 Thread Matthew Seaman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gary Kline wrote:

   I booted into single-user (press 4) and got rid of tons of junk
   left in /var/tmp.  Then I did a mount -a and and fsck -y.

But not in that order.  fsck -y *first*, then mount -a, then start
removing files from /var/tmp.

Matthew

- -- 
Dr Matthew J Seaman MA, D.Phil.   7 Priory Courtyard
  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
  Kent, CT11 9PW
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.3 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGSpfy8Mjk52CukIwRCPsuAJsFQwT+G5APT3a4XccFcmODfYXMlQCfYCQR
BI5cpzCkfYKOkFfSCGo9HvQ=
=VlWP
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]