SORRY. NO SPACE IN lost+found DIRECTORY
___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SORRY. NO SPACE IN lost+found DIRECTORY
Sorry, no contents in email. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No space in lost+found directory (formerly: SORRY. NO SPACE IN lost+found DIRECTORY)
Pasted from subject: 2009/4/16 vijay kumar vijay.ku...@nirvanainfocom.com: SORRY. NO SPACE IN lost+found DIRECTORY Please don't shout. Have you checked that / has sufficient space? Try root # fsck / --- root # df -h and post the result. Regards, Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No space in lost+found directory (formerly: SORRY. NO SPACE IN lost+found DIRECTORY)
On Thu, 16 Apr 2009 14:03:58 +0100 Chris Rees utis...@googlemail.com wrote: 2009/4/16 vijay kumar vijay.ku...@nirvanainfocom.com: SORRY. NO SPACE IN lost+found DIRECTORY Please don't shout. fsfsck_ffs/dir.c:467: pfatal(SORRY. NO SPACE IN lost+found DIRECTORY Maybe we should tell FreeBSD to stop shouting too? :) -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No space in lost+found directory (formerly: SORRY. NO SPACE IN lost+found DIRECTORY)
2009/4/16 Bruce Cran br...@cran.org.uk: On Thu, 16 Apr 2009 14:03:58 +0100 Chris Rees utis...@googlemail.com wrote: 2009/4/16 vijay kumar vijay.ku...@nirvanainfocom.com: SORRY. NO SPACE IN lost+found DIRECTORY Please don't shout. fsfsck_ffs/dir.c:467: pfatal(SORRY. NO SPACE IN lost+found DIRECTORY Maybe we should tell FreeBSD to stop shouting too? :) -- Bruce Cran Actually, we really should! Come on, we're not on teletypes any more. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No space in lost+found directory (formerly: SORRY. NO SPACE IN lost+found DIRECTORY)
On Thu, 16 Apr 2009 15:21:28 +0100, Chris Rees utis...@googlemail.com wrote: 2009/4/16 Bruce Cran br...@cran.org.uk: Maybe we should tell FreeBSD to stop shouting too? :) Actually, we really should! Come on, we're not on teletypes any more. Did UPPERCASE LETTERS make the teletype print louder? I always assumed they would just consume more disk space... RYRYRYRYRYRYRY!!! :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No space in lost+found directory (formerly: SORRY. NO SPACE IN lost+found DIRECTORY)
On Thu, Apr 16, 2009 at 08:30:40PM +0200, Polytropon wrote: On Thu, 16 Apr 2009 15:21:28 +0100, Chris Rees utis...@googlemail.com wrote: 2009/4/16 Bruce Cran br...@cran.org.uk: Maybe we should tell FreeBSD to stop shouting too? :) Actually, we really should! Come on, we're not on teletypes any more. Did UPPERCASE LETTERS make the teletype print louder? I always assumed they would just consume more disk space... RYRYRYRYRYRYRY!!! :-) Nah, the earliest ones only had upper case. When they made upper/lower models, for some reason people just left on shift-lock - maybe to make it look the same. jerry -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SORRY. NO SPACE IN lost+found DIRECTORY
While trying to recover from a HD crash, 'fsck -y /dev/rad1s1a' reports the following error a number of times at the end of it's run. UNREF FILE I=3537799 OWNER=500 MODE=100644 SIZE=6611 MTIME=Oct 25 21:12 2003 RECONNECT? yes SORRY. NO SPACE IN lost+found DIRECTORY This tells me that it's not saving some of the files on the drive. Is that correct? Is there anything I can do to make more space in lost+found, either system-wide or while the fsck is running? Some possibly pertinent info: # ls -lad lost+found drwxrwxrwt 1379 root wheel 182272 Apr 12 16:55 lost+found # ls lost+found | wc -l 8899 This fs was copied from a drive reporting hard errors reading fsbn... using dd. Thanks, Brad Waite ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
