Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during fs recovery).
In FreeBSD 9, I found lost+found dir under /mnt
On Tue, Mar 13, 2012 at 2:58 AM, jb jb.1234a...@gmail.com wrote:
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad
hoc
e.g. at boot time
On Tue, 13 Mar 2012 07:58:09 + (UTC), jb wrote:
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
Correct.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during
jb jb.1234a...@gmail.com wrote:
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during fs recovery).
In FreeBSD 9
...@videotron.ca wrote:
[~]# cd /tmp/lost+found/#123456
[/tmp/lost+found/#123456]# ls
Okay, it's empty.
[/tmp/lost+found/#123456]# cd ..
Strange, why does .. lead you from /tmp/lost+found/#123456
to /tmp/lost+found/#123456, just as if cd wasn't executed?
[/tmp/lost+found
On Sat, May 02, 2009 at 11:06:27PM +0200, Polytropon typed:
On Sat, 02 May 2009 15:45:13 -0400, PJ af.gour...@videotron.ca wrote:
[~]# cd /tmp/lost+found/#123456
[/tmp/lost+found/#123456]# ls
Okay, it's empty.
[/tmp/lost+found/#123456]# cd ..
Strange, why does .. lead you from
On Mon, 4 May 2009 11:08:04 +0200, Ruben de Groot mai...@bzerk.org wrote:
Probably because the # is interpreted as comment. I can reproduce this
in a bourne shell; not in (t)csh.
Ah, thank you. According to the prompt, it didn't look
like csh in the first place, but not like plain sh, too.
A couple of days ago I had minor glitch as my FreeBSD box on my local
intranet had an unexpected shutdown.
When I fsck'd on reboot I was left with a few lost+found directories
with #99 files. Most appeared inconsequential and could be deleted.
But there is one /tmp/lost+found that puzzles me
On Sat, 02 May 2009 15:45:13 -0400, PJ af.gour...@videotron.ca wrote:
[~]# cd /tmp/lost+found/#123456
[/tmp/lost+found/#123456]# ls
Okay, it's empty.
[/tmp/lost+found/#123456]# cd ..
Strange, why does .. lead you from /tmp/lost+found/#123456
to /tmp/lost+found/#123456, just as if cd wasn't
___
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 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
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
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
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
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
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
ran 'fsck -t ufs -y'. all seemed fine and dandy until I tried to remount the
volume after bringing it back to multi-user mode. The disk space was occupied,
but it all resided in lost+found with names like : #001 , #002
etc... !! Each file was multiple gigabytes worth of data
Yesterday my server rebooted for some unknown reason and after fsck-
ing 4 times I had ALOT of stuff in lost+found. I really need to try
and review/recover these files. Only docs I've found were linux
centric, and focused on directories and dates. I can't make out
either here.
Please
Hello,
What is lost+found? I've got one on all my filesystems and over the past
few days i've had things being deleted from there. Do i have a problem?
Thanks.
Dave.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman
In response to Dave [EMAIL PROTECTED]:
Hello,
What is lost+found? I've got one on all my filesystems and over the past
few days i've had things being deleted from there. Do i have a problem?
When fsck finds problems with the filesystem, it saves any data that otherwise
may have been lost
Bill Moran writes:
What is lost+found? I've got one on all my filesystems and
over the past few days i've had things being deleted from
there. Do i have a problem?
When fsck finds problems with the filesystem, it saves any data
that otherwise may have been lost
Yesterday after an fsck a file was placed in the lost+found folder which
size was exactly the size of the drive (450gb). What is the safest way
to remove this file?
Thanks,
Scott Oertel
___
freebsd-questions@freebsd.org mailing list
http
In the last episode (Aug 02), Scott Oertel said:
Yesterday after an fsck a file was placed in the lost+found folder which
size was exactly the size of the drive (450gb). What is the safest way
to remove this file?
If its timestamp updates when you touch a file on the main filesystem,
it's
Dan Nelson wrote:
In the last episode (Aug 02), Scott Oertel said:
Yesterday after an fsck a file was placed in the lost+found folder which
size was exactly the size of the drive (450gb). What is the safest way
to remove this file?
If its timestamp updates when you touch a file
In the last episode (Aug 02), Scott Oertel said:
Dan Nelson wrote:
In the last episode (Aug 02), Scott Oertel said:
Yesterday after an fsck a file was placed in the lost+found folder
which size was exactly the size of the drive (450gb). What is the
safest way to remove this file?
If its
Dan Nelson wrote:
In the last episode (Aug 02), Scott Oertel said:
Dan Nelson wrote:
In the last episode (Aug 02), Scott Oertel said:
Yesterday after an fsck a file was placed in the lost+found folder
which size was exactly the size of the drive (450gb). What is the
safest way
Hello Chuck,
Jerlique Bahn wrote:
If I pull the power on my server whilst its doing heavy IO, should I get
files in lost+found if my raid card has battery backed cache?
Yes, it's still possible.
The cache on the RAID card will be flushed OK, but any in-process
operations by live
Hello,
If I pull the power on my server whilst its doing heavy IO, should I get
files in lost+found if my raid card has battery backed cache?
I was under the understanding that the file operations were atomic, and
hence freebsd's file system should have no corrupted files on the reboot
Jerlique Bahn wrote:
If I pull the power on my server whilst its doing heavy IO, should I get
files in lost+found if my raid card has battery backed cache?
Yes, it's still possible.
I was under the understanding that the file operations were atomic, and
hence freebsd's file system should
Hi.
Why the structure of directories in FreeBSD don't have a lost+found
directory?. (Talking about 6.x Releases)
Some Unix manuals tell that this directory is very important for the
work of the fsck program...
Thanks very much, in advance.
Regards.
Jose.
--
http://www.lordofunix.org
On Sat, May 13, 2006 at 11:42:54PM +0200, Jose Luis Alarcon Sanchez wrote:
Hi.
Why the structure of directories in FreeBSD don't have a lost+found
directory?. (Talking about 6.x Releases)
Some Unix manuals tell that this directory is very important for the
work of the fsck program
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
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
Hi everyone:
On one of my disks that has no files in it mounted as /mnt/usr,
fsck is creating the lost+found directory and underneath each one are
directories named starting with # that is empty, is there anyway to remove
these? Thanks.
[EMAIL PROTECTED] [10:26am][/mnt/usr/lost+found
On Sat, Mar 06, 2004 at 08:27:11AM -1000, Vincent Poy wrote:
Hi everyone:
On one of my disks that has no files in it mounted as /mnt/usr,
fsck is creating the lost+found directory and underneath each one are
directories named starting with # that is empty, is there anyway to remove
On Sat, 6 Mar 2004, Kris Kennaway wrote:
On Sat, Mar 06, 2004 at 08:27:11AM -1000, Vincent Poy wrote:
Hi everyone:
On one of my disks that has no files in it mounted as /mnt/usr,
fsck is creating the lost+found directory and underneath each one are
directories named starting
On Sat, Mar 06, 2004 at 02:00:12PM -1000, Vincent Poy wrote:
They're just directories, remove them in the usual way.
Tried that, didn't work...
[EMAIL PROTECTED] [4:00pm][/mnt/usr/lost+found] rm -rf *
rm: #5558272: Directory not empty
rm: #7018496: Directory not empty
rm
On Sat, 6 Mar 2004, Kris Kennaway wrote:
On Sat, Mar 06, 2004 at 02:00:12PM -1000, Vincent Poy wrote:
They're just directories, remove them in the usual way.
Tried that, didn't work...
[EMAIL PROTECTED] [4:00pm][/mnt/usr/lost+found] rm -rf *
rm: #5558272: Directory not empty
][/mnt/usr/lost+found] rm -rf *
rm: #5558272: Directory not empty
rm: #7018496: Directory not empty
rm: #7206914: Directory not empty
rm: #7254025: Directory not empty
rm: #7254167: Directory not empty
Unmount the filesystem and run fsck again (e.g. with the -f flag).
You seem
that, didn't work...
[EMAIL PROTECTED] [4:00pm][/mnt/usr/lost+found] rm -rf *
rm: #5558272: Directory not empty
rm: #7018496: Directory not empty
rm: #7206914: Directory not empty
rm: #7254025: Directory not empty
rm: #7254167: Directory not empty
Unmount
On Sat, Mar 06, 2004 at 04:03:35PM -1000, Vincent Poy wrote:
They're just directories, remove them in the usual way.
Tried that, didn't work...
[EMAIL PROTECTED] [4:00pm][/mnt/usr/lost+found] rm -rf *
rm: #5558272: Directory not empty
rm: #7018496
On Sat, 6 Mar 2004, Kris Kennaway wrote:
On Sat, Mar 06, 2004 at 04:03:35PM -1000, Vincent Poy wrote:
They're just directories, remove them in the usual way.
Tried that, didn't work...
[EMAIL PROTECTED] [4:00pm][/mnt/usr/lost+found] rm -rf *
rm: #5558272
][/mnt/usr/lost+found] rm -rf *
rm: #5558272: Directory not empty
rm: #7018496: Directory not empty
rm: #7206914: Directory not empty
rm: #7254025: Directory not empty
rm: #7254167: Directory not empty
Unmount the filesystem and run fsck again (e.g
Hi,
I had a server which due to power problems rebooted a couple of times. I did
a fsck, because it kept complaining about inconsistencies.
Now some directories seem to have moved. I located them in lost + found. Is
there any way to recover these files from there ??
thanks
Doron
On Tue, Nov 19, 2002 at 12:10:33PM +0200, Doron Shmaryahu wrote:
I had a server which due to power problems rebooted a couple of times. I did
a fsck, because it kept complaining about inconsistencies.
Now some directories seem to have moved. I located them in lost + found. Is
there any way
45 matches
Mail list logo
