Khaladaadka aan sabab cad lahayn ayaa ah dhibaatooyinka ugu xanaaqa badan ee wax ka qabashada. Iyo halka Linux inta badan ay gaar u tahay farriimaha khaladka ah, tani waa mid ka mid ah dhowr jeer marka ay kubbadda tuurto.

Helitaanka "Ma jirto meel looga tagey qaladka qalabka" wax yar ayaa sharxayaa, gaar ahaan haddii darawalkaagu uu ka fog yahay mid buuxa. Waa maxay sababta fariintan khaladku u soo baxayso? Waa maxay sababta aadan u abuuri karin faylal cusub in kasta oo aad boos ku filan diskka ku leedahay? Iyo tan ugu muhiimsan, sidee ayaad u hagaajinaysaa?

Aan ogaano.

Dhab ahaantii Hard Drive -kaagu ma leeyahay meel ku filan^{(Hard Drive Actually Have Enough Space)} ?

Kahor intaadan ku degdegin inaad wax hagaajiso, hubi inay dhibaato jirto, si aad u bilawdo. Ka dib oo dhan, haddii booska diskooga uu dhab ahaantii ka dhammaaday nidaamkaaga, looma baahna in la argagaxo. Waxaad kaliya ka saari kartaa xogta aan loo baahnayn si aad u xorayso meel badan.

Waxaa jira laba amar oo Linux ah oo loogu talagalay helitaanka macluumaadka ku saabsan booska diskka - du iyo df. Amarka du wuxuu qiyaasaa isticmaalka booska diskka, halka taliska df uu falanqeeyo booska bilaashka ah ee ku yaal saxanka. Isticmaalka iyaga oo la socda sudo waxay ku siinaysaa warbixin sax ah oo ku saabsan inta boos ee dhab ahaantii laga heli karo saxanka.

1. Aan ku bilowno amarka du. Wax soo saarkeedu waxa uu noqon karaa mid dheer oo dhib badan in la maro, markaa waxaanu isticmaali doonaa -s iyo -h calanka. -s waxay soo koobaysaa natiijooyinka, halka -h ay hubiso inay tahay mid bini'aadamku akhrin karo. Markaa geli amarka sudo du -sh / meesha / tilmaamaya hagaha saldhigga.

1. Ha ka werwerin dhammaan fariimaha la diiday ee oggolaanshaha - taasi waa sida ay u dhex marto dhammaan haga-hoosaadyada nidaamka. Iyada oo ku xidhan inta uu le'eg yahay darawalku waxa laga yaabaa in aad ka tagto isaga oo soconaaya muddo, maadaama uu si isdaba joog ah wax walba u marayo.

1. Marka du ay dhameysato iskaanka, waxay soo saari doontaa liis fudud oo hagayaal ah oo ay weheliso cabbirkooda. Tusaale ahaan, kani waa soo-saarka amarka du ee lagu dabaqay hagaha caadiga ah.

Hadda waxaan isticmaali doonaa df si aan u aragno inta boos ee bilaashka ah ee la heli karo. Amarka df aad ayuu u fudud yahay in la isticmaalo maadaama ay kaliya tusinayso nidaamyada faylalka ku rakiban iyo xisaabaadka isticmaalkooda. Mar labaad, waxaan isticmaali doonaa calanka -h si aan uga dhigno wax soo saarka aadanaha mid la akhriyi karo.

sudo df -h

Fikradda ayaa ah in la tiriyo natiijooyinka du iyo amarrada df. Kala duwanaansho kastaa waxay tilmaamaysaa booska diskka oo aan si xor ah loo heli karin inkasta oo aan la isticmaalin wax faylal ama gal ah.

Waa maxay sababta Linux u muujiso^{(Does Linux Show)} "Ma jirto meel looga tagey^{(Space Left)} aaladda"?

Haddii aad arkayso fariinta khaladka ah ee "No Space Left on Device" in kasta oo aad ku haysato meel banaan oo ku filan saxankaaga, khaladku maaha qalabka. Ogaanshaha sababta saxda ah ee khaladku waxay qaadan kartaa xoogaa cilad-baadhis ah.

• Faylka Dhawaan La Tiray: Sababta ugu badan ee loo arko qaladkan waa fayl dhawaan la tirtiray. Inta badan feylku waa la tirtiraa iyadoo hawsha weli la isticmaalayo, iyada oo meel bannaan lagu hayo inkasta oo feylku hore u baxay.
• Aan ku filnayn Inodes^{(Enough Inodes)} : Sababta kale ee soo noqnoqda waa la'aanta inodes^(inodes) ku filan . Inodes waa boggaga tusmada ee nidaamka faylka Unix , oo haya xogta badan ee fayl kasta ee kaydinta. Si kastaba ha ahaatee, inodes-ku maaha mid aan xadidnayn, oo dhammaanaya inodes ka hor inta aysan booska kaydinta ku siin karin qaladka "No space left on device".
• Ku guuldareysiga Hard Drive-ka: Markaa dabcan waxaa jirta suurtagalnimada in Hard Drive-ku si fudud u fashilmo, inta badan ee bannaan ee muuqatana waxaa qaata qaybo xun. Maadaama nidaamku ku guuldareysto inuu u qoro wax faylal ah goobahan, waxay tuuraysaa qalad.

Hagaajinta 1: Dib u bilaw habsocodyada adoo isticmaalaya faylasha la tirtiray^{(Using Deleted Files)}

Sababta ugu macquulsan ee qaladka "Ma jirto meel bannaan oo qalab ah" waa habka weli isticmaalaya faylka la tirtiray. Mahadsanid, hagaajinta qaladkan waa sahlan tahay. Kaliya waxaad u baahan tahay inaad dib u bilowdo habka^{(restart the process)} si aad u xorayso kaydinta kaydsan.

1. Si aad u hesho habka dhibka leh, waxaad u baahan tahay inaad isticmaasho amarrada lsof iyo grep. Amarka lsof wuxuu ku siin doonaa liiska dhammaan faylalka furan ee loo isticmaalo hababka socodsiinta, iyo grep wuxuu hoos u dhigi karaa xulashada kuwa la tirtiray. Markaa geli sudo lsof / | grep waa la tirtiray halka / ay tahay buugga hagaha iyo | tuubo isku xidha wax soo saarka lsof iyo grep.

1. Hadda waxaad dib ugu bilaabi kartaa habka ay saamaysay sudo systemctl dib u bilaw adeegga_name amarka, halkaas oo magaca adeeggu yahay magaca adeegga soo baxay raadinta.

1. Haddii ay jiraan habab badan oo sidan oo kale ah ama aadan rabin inaad ku dhibto helitaanka adeegyo gaar ah, waxaad dib u dejin kartaa dhamaantood sudo systemctl daemon-reload Command. Tani waxay dib u soo noolaynaysaa dhammaan ku tiirsanaanta, iyada oo la tixgelinayo isbeddel kasta oo ku yimaadda nidaamka faylka.

Taas ka dib booska kaydinta ee lagu hayo habka waa in mar kale la helaa, taas oo kuu ogolaanaysa inaad qorto faylasha adigoon ku dhicin wax qalad ah.

Hagaajinta 2: Hubi Inodes

Iyadoo darawal kasta uu leeyahay tiro badan oo inodes ah, waa mid xadidan. Oo haddii nidaamkaaga lagu daadiyo tiro cajiib ah oo faylal ah, waxaa suurtagal ah in la gaaro xadkan ka hor inta aan la daalin awoodda kaydinta darawalka. Tani waa sababta ay u wanaagsan tahay in la haysto faylal waaweyn halkii aad ka heli lahayd kuwa aad u yaryar.

Waxaad si fudud u hubin kartaa helitaanka inodes adiga oo isticmaalaya calanka -i oo leh amarka df. Sida tan:

sudo df -i

Tani waxay si cad u sheegi doontaa tirada guud ee inodes ee ku jira nidaamka faylalka, oo ay la socoto cadadka hadda la isticmaalo. Haddii aysan jirin wax-ka-baxyo bilaash ah oo ku haray nidaamkaaga, tani waa isha laga helo qaladka "Ma jirto meel looga tagey qalabka".

Maadaama inodes kaliya la abuuray marka ugu horeysa ee la qaabeeyo darawalka, ma jirto hab lagu soo saaro inodes dheeraad ah. Waxa kaliya ee aad samayn karto waa in aad tirtirto faylal kasta oo aan loo baahnayn si aad u xorayso inodes ee faylasha mustaqbalka.

Hagaajinta 3: Calaamadee Blocks xun

Musuqmaasuqa xogtu^(Data) waa masiirka lama huraanka ah ee darawal kasta oo adag. In kasta oo darawalka cusubi aanu ku socon doonin arrintan, Hard disks-yadii hore waxay si tartiib tartiib ah u bilaabi doonaan inay "xun".

Tani waxay ka dhigan tahay in qaybo ka mid ah darawalka adag laga dhigay mid aan la isticmaali karin, inkastoo nidaamka faylalka uu weli u arko inay shaqeynayaan. Baloogyadan xun waxay si been abuur ah u buufiyaan meesha bannaan ee bannaan ee wadista, marka run ahaantii aan wax faylal ah loo qori karin. Tani waxay keenaysaa qalad "Ma jirto meel looga tagey qalabka", maadaama nidaamka hawlgalka uu isku dayayo oo uu ku guuldareysto inuu kaydiyo wax xog ah oo ku saabsan goobahan.

Ma jirto hab dhab ah oo lagu hagaajin karo arrintan, maadaama qaybaha xun ay yihiin natiijada daalka jirka iyo jeexjeexa darawalka adag. Waxa kaliya ee aad sameyn karto waa calaamadee qaybaha xun si aysan mar dambe u tixraacin nidaamka faylka.

Tani waxay u baahan tahay inaad ka boot CD Live^{(Live CD)} ah , maadaama aadan samayn karin nidaamka File System Check^{(File System Check)} gudaha drive socda. Markaad taas sameyso, isticmaal kaliya amarka soo socda:

sudo fsck -vcck /dev/sda

Tani waxay ku beddeshaa /dev/sda dariiqa wadista aad rabto inaad hagaajiso. Tani waxay si otomaatig ah u ogaan doontaa dhammaan baloogyada xun ee darawalka waxayna calaamadin doontaa inay yihiin kuwo aan la isticmaali karin. Si kastaba ha ahaatee, kuma siin doonto wax awood kaydin oo dheeraad ah, si kastaba ha ahaatee, u diyaargarow inaad nadiifiso qaar ka mid ah faylalka aan faa'iido doonka ahayn si aad u xorayso booska wadista.

Waa maxay Habka ugu Wanaagsan ee lagu Hagaajin karo Qaladka "Ma banaana Aalladda"?

Sababta caadiga ah ee lagu arko qaladka "Ma banaana qalabka" ee Ubuntu ama wixii kale ee Linux distro waa faylka la tirtiray oo weli loo isticmaalo habka socodsiinta. Tani waxay kaydinaysaa kaydinta uu ku jiray feylku, iyada oo ka hortagaysa hawlgallada kale inay xogta u qoraan goobtaas.

Hagaajinta dhibaatadan sidoo kale waa tan ugu fudud, sida dhammaan waxaad u baahan tahay inaad sameyso waa inaad dib u bilowdo nidaamka su'aasha. Sababaha kale ee qaladka, si kastaba ha ahaatee, ma aha kuwa fudud in la xalliyo.

Haddi ay darawalkaagu ay dhiban yihiin xogaha xunxun ama uu ka dhamaaday inodes, ma jirto hab toos ah oo lagu xaliyo arimahan. Waa inaad tirtirtaa faylalka jira si aad boos ugu heshid in xog cusub la qoro.

Top 3 Ways to Fix “No Space Left on Device” Error in Linux

Errors without a cleаr cause are the most irritating problems to deal with. And while Linux is usually ѕpecific in its error messages, this iѕ one of the few times when it drops the ball.

Getting a “No place left on device error” explains very little, especially if your drive is far from full. Why is this error message showing up? Why can’t you create new files despite having sufficient space on the disk? And most importantly, how do you fix it?

Let’s find out.

Does Your Hard Drive Actually Have Enough Space?

Before you rush to find a fix, make sure there is a problem, to begin with. After all, if disk space has actually run out on your system, there is no need to panic. You can just remove unnecessary data to free up more space.

There are two Linux system commands for getting information about disk space – du and df. The du command estimates the disk space usage, while the df command analyzes the free space present on the disk. Using them in conjunction with sudo gives you an accurate report of how much space is actually available on the disk.

1. Let’s start with the du command. Its output can be rather long and cumbersome to go through, so we will use the -s and -h flags. -s summarizes the results, while -h ensures it is human readable. So enter the command sudo du -sh / where / points to the base directory.

1. Don’t worry about all the permission denied messages – that’s how it trawls through all subdirectories of the system. Depending on the size of the drive you may have to leave it running for a while, as it recursively goes through everything.

1. When du finishes scanning, it will output a simple list of directories alongside their sizes. For example, this is the output of the du command applied to an ordinary directory.

Now we will use df to see how much free space is available. The df command is much simpler to use since it only shows the mounted filesystems and their usage statistics. Once again, we will use the -h flag to make the output human readable.

sudo df -h

The idea is to tally the results of the du and df commands. Any discrepancy points to disk space that is not freely available despite not being used by any files or folders.

Why Does Linux Show “No Space Left on Device”?

If you are seeing the “No Space Left on Device” error message despite having sufficient free space on your disk, it’s not the hardware that’s at fault. Figuring out the exact cause for the error can take a bit of troubleshooting.

• Recently Deleted File: The most common reason for seeing this error is a recently deleted file. Often a file is deleted while a process is still using it, keeping the space reserved even though the file is already gone.
• Not Enough Inodes: Another frequent cause is not having enough inodes. Inodes are the index pages of a Unix filesystem, holding the metadata of every file on storage. However, inodes aren’t unlimited, and running out of inodes before the storage space can give you the “No space left on device” error.
• Failing Hard Drive: Then of course there is the possibility that the hard drive is simply failing, and much of the apparent free space is taken up by bad sectors. Since the system fails to write any files to these locations, it throws an error.

Fix 1: Restart Processes Using Deleted Files

The most probable cause of the “No space left on device” error is a process still using a deleted file. Thankfully, fixing this error is easy. You just need to restart the process to free up the reserved storage.

1. To find the problematic process, you need to use the lsof and grep commands. The lsof command will give you a list of all open files being used by running processes, and grep can narrow down the selection to the ones that are deleted. So enter sudo lsof / | grep deleted where / is the base directory and | a pipe for linking lsof’s output to grep.

1. Now you can restart the affected process with the sudo systemctl restart service_name command, where the service name is the name of the service that turned up in the search.

1. If there are multiple processes like this or you just don’t want to bother with finding specific services, you can just reset them all with the sudo systemctl daemon-reload command. This regenerates all dependencies, taking any changes in the filesystem into account.

After this the storage space being held up by the process should be available again, allowing you to write files without running into any errors.

Fix 2: Check Inodes

While each drive has a large number of inodes, it is finite. And if your system is littered with an incredible number of files, it is possible to reach this limit before exhausting the storage capacity of the drive. This is why it’s better to have large files rather than too many small ones.

You can easily check the availability of inodes by using the -i flag with the df command. Like this:

sudo df -i

This will clearly tell the total number of inodes present in the filesystem, along with the amount currently in use. If there are no free inodes left on your system, this is the source of the “No space left on device” error.

As inodes are only created upon first formatting the drive, there is no way to generate more inodes. All you can do is delete any unnecessary files to free up inodes for future files.

Fix 3: Mark Bad Blocks

Data corruption is the inevitable fate of any hard drive. While a new drive will not run into this issue, older hard disks will gradually start going “bad”.

What this means is that portions of the hard drive are rendered unusable, even though the filesystem still considers them functional. These bad blocks falsely inflate the apparent free space on the drive, when in truth no files can be written to them. This leads to a “No space left on device” error, as the operating system tries and fails to store any data on these locations.

There is no real way to fix this issue, as bad sectors are a result of the physical wear and tear of a hard drive. The only thing you can do is mark the bad sectors so that they are no longer referenced by the file system.

Doing this requires you to boot from a Live CD, as you cannot perform a File System Check within a running drive. Once you do that, just use the following command:

sudo fsck -vcck /dev/sda

This replaces the /dev/sda with the path of the drive you want to repair. This will automatically detect all bad blocks on the drive and mark them as unusable. It won’t give you any extra storage capacity, however, so be prepared to clean up some useless files to free up space on the drive.

What Is the Best Way to Fix the “No Space Left on Device” Error?

The usual reason for seeing a “No space left on device” error on Ubuntu or any other Linux distro is a deleted file still being used by a running process. This reserves the storage that was occupied by the file, preventing other operations from writing data to that space.

Fixing this problem is also the easiest, as all you need to do is to restart the process in question. The other causes of the error, however, are not that easy to solve.

Whether your drive is plagued by bad data blocks or has run out of inodes, there is no direct way to fix these issues. You must delete existing files to make room for new data to be written.

Related posts

• 8 siyaabood oo lagu hagaajin karo "Ma haysatid ogolaansho inaad ku kaydsato goobtan" qaladka Windows

• Hagaaji "Eraygu Ma Bilaaban Karo Beddelka MSWRD632.WPC/SSPDFCG_x64.CNV" Khaladka

• Hagaaji "Ma bilaabi karo Microsoft Office Outlook" Khaladka

• Sida loo hagaajiyo "Ma Raad Karaa Sawirka. Taabo si aad dib isugu daydo"Instagram Khaladka

• Sida loo hagaajiyo "Windows ma geli karo Jidka Qalabka ama Faylka Gaarka ah" Khaladka

• 6 Siyaabood Oo Fudud Oo Lagu Kordhiyo Ku rakibkaaga Ubuntu

• Sida loo hagaajiyo "Ma Abuuri karin Mashiinka Virtual Java" Khaladka

• Sida loo hagaajiyo "Ma buuxin kari waynay Cusbooneysiinta" Cilad ku jirta Windows

• Sida loo hagaajiyo Outlook's "Waan ka xunahay, dhib ayaa naga haysata furitaanka shaygan" Khalad

• 9 siyaabood oo lagu hagaajin karo "Systemkaagu wuu ka dhamaaday Application Memory" ee Mac

• 13 siyaabood oo loo hagaajiyo "Fariintan lagama soo dejin Server-ka" ee iPhone iyo iPad

• 9 siyaabood oo lagu hagaajin karo OneDrive ”Soo rarku waa la xannibay” khaladaadka gudaha Windows

• 10ka Hab ee ugu Wanaagsan ee lagu Hagaajin karo Koodhka Qaladka Netflix M7353-5101

• Hagaaji "Xeerka Nabadgelyada Aan Sax ahayn" Khaladka iTunes

• 8 siyaabood oo loo hagaajiyo "Aw, Snap!" Khaladaadka Bogga ee Chrome

• Hagaaji Aalladdaga kuma habboona Ciladda Noocan

• Sida loo hagaajiyo Discord's "Rote No" qalad

• 5 siyaabood oo lagu hagaajin karo GTA 5 Cilada Xusuusta Ciyaarta

• Fix "Qalabka shabakadda wireless-ka ee aan la taageerin waa la helay. Nidaamkii waa la joojiyay" Khaladka

• Hagaaji qaladka Netflix "Lama xiriiri karo Netflix"