Not sure you can it is there to hold broken stuff picked up by fsck programs. In the past it was creted if needed but recently it seem to be a built in.
There is 24 gig in the folders??? that does not make sense. only broken files go there did you have a crash???
In any case you can delete stuff from the folders you would need to be root.
I do not quite understand you. You spelled this in three different ways (“lost & found”, “Lost &found” and “Lost&Found”). only one at the most can be correct.
Do you mean the lost+found directory that is used by many file system type? Like:
boven:~ # ls -ld /home/lost+found/
drwx------ 2 root root 4096 Oct 25 2009 /home/lost+found/
boven:~ #
And after a low level format, you will have nothing usefull on the disk. Not even a partition table, let alone a file system, let alone a lost+found directory.
I assume you must explain much more when you want that we understand what you have, did, see, are doing and want to have done.
On 04/18/2013 12:06 PM, lanzaroteman wrote:
>
> gogalthorp;2548829 Wrote:
>> Not sure you can it is there to hold broken stuff picked up by fsck
>> programs. In the past it was creted if needed but recently it seem to be
>> a built in.
>
> Thanks for reply,It would be a waste 24 gig diskspace ifnot
> But will not even allow a new folder.
>
> I am sure that that someone will know how.
Why do you think there is 24 GB in lost+found? Is that from “du”? My file system
that contains / only has 16 blocks in its lost+found.
If it really is big, then you can delete (with sudo) the files in that
directory, even if that directory cannot be removed.
Just delete the files inside. Removing the directory itself may not be possible. It may require root permission to do that.
If there is 24 gig in lost&found you had a serious problem those are files and pieces of files that were pickup out of a crashed files system. Though whole files ad directories might be intact most things will just be junk and non recoverable at least to most mortals.
Is that clear ie just delete the files leave the directory
> I need a clean disk for storage.
> Lost+Found is not needed or wanted.
It is needed and wanted by the system, you can not delete it.
Even if it is a clean data disk, it is needed.
You can empty it, if it contains something. If there is something
inside, it means you had a filesystem disaster, so you have to explain
to us what kind of disaster you had.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 04/18/2013 03:08 PM, Carlos E. R. wrote:
> On 2013-04-18 20:24, lanzaroteman wrote:
>
>> OK its lost+found.
>>
>> Gparted tells me that 24 gb is used.
>
> Prove it. Photo, please. Or better, run this and paste it all in here,
> inside a code tags block:
>
>
> fdisk -l
> df -h
>
>
> Please use code tags for printouts and commands. Advanced editor, ‘#’
> button. > Posting in Code Tags - A Guide](http://forums.opensuse.org/showthread.php?t=451526)
>
>
>
>> I need a clean disk for storage.
>> Lost+Found is not needed or wanted.
>
> It is needed and wanted by the system, you can not delete it.
> Even if it is a clean data disk, it is needed.
>
> You can empty it, if it contains something. If there is something
> inside, it means you had a filesystem disaster, so you have to explain
> to us what kind of disaster you had.
Am 18.04.2013 22:24, schrieb Jim Henderson:
> You may not “need or want” it, but the filesystem you’ve formatted the
> drive with does actually need it.
and that is also the answer, if one does not need and want it use a file
system which does not have it like xfs instead of ext4.
–
PC: oS 12.3 x86_64 | i7-2600@3.40GHz | 16GB | KDE 4.10.0 | GTX 650 Ti
ThinkPad E320: oS 12.3 x86_64 | i3@2.30GHz | 8GB | KDE 4.10.0 | HD 3000
HannsBook: oS 12.3 x86_64 | SU4100@1.3GHz | 2GB | KDE 4.10.0 | GMA4500
On 2013-04-18 22:41, Martin Helm wrote:
> Am 18.04.2013 22:24, schrieb Jim Henderson:
>> You may not “need or want” it, but the filesystem you’ve formatted the
>> drive with does actually need it.
>
> and that is also the answer, if one does not need and want it use a file
> system which does not have it like xfs instead of ext4.
My /usr is xfs and has an “/usr/lost+found/”. I have more xfs
partitions, but that’s the only one with it, possibly because it
contains files. I think it is created (xfs) when a recovery operation
needs it.
Or I could be mistaken, because at some time that /usr was ext3 and I
migrated it, forgetting to delete that folder.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Am 18.04.2013 23:08, schrieb Carlos E. R.:
> My /usr is xfs and has an “/usr/lost+found/”. I have more xfs
> partitions, but that’s the only one with it, possibly because it
> contains files. I think it is created (xfs) when a recovery
> operation needs it.
>
> Or I could be mistaken, because at some time that /usr was ext3 and
> I migrated it, forgetting to delete that folder.
>
My /home and / on the machine where I am typing right now are both xfs,
/boot is ext4.
/boot has lost+found, neither /home nor / have it.
Thank you you have answered the problem.
Dban and killdisk did remove it but formating ex4 replaced it.
To moderators who get personal with replies, not all users that come here
for help are able to do the things you ask,some like me use voice commands to stay in contact with
with the world.
entering data for me is slow and sometimes painful .
For any one that might have the same problem.
I have just formated a 3tb disk exfat which works
fine a seem to be a little faster.
Also fdisk does not work on gpt large volums
I don;t think exfat is supported could be wrong never heard of it being used in the Linux environment.
In any case it will not work as a base file system for a Linux system it simply does not have a proper set of permissions. It can be used for a storage area or shared storage between Windows and Linux. Don’t use it as home or root
use gdisk it is known the fdisk does not work with GPT disks and any over 2 gig