I've just had a message today from Ubuntu 11.04 that I have only 100 MB left, so I cleaned up some files, and I got 200 MB. Then, after a couple of hours, suddenly I have only 26 MB?! I tried df, du via mount --bind, /forcefsck with reboot - nothing could should what the culprit is - finally I searched big files, realized /var/log/syslog is 100MB+ and /var/log/kern.log is 200MB+ - blanked them with sudo bash -c 'echo &gt; ...' and rebooted, and now I have some spare MB.  But now, I realize I have another problem with df:  $ df -h Filesystem            Size  Used Avail Use% Mounted on /dev/sda5             9,7G  8,8G  385M  96% / none                  963M  696K  962M   1% /dev none                  969M   12K  969M   1% /dev/shm none                  969M  252K  969M   1% /var/run none                  969M     0  969M   0% /var/lock /dev/sda6             9,7G  8,1G  1,1G  89% /media/disk  $ df -h --block-size M Filesystem           1M-blocks      Used Available Use% Mounted on /dev/sda5                9845M     8960M      385M  96% / none                      963M        1M      962M   1% /dev none                      969M        1M      969M   1% /dev/shm none                      969M        1M      969M   1% /var/run none                      969M        0M      969M   0% /var/lock /dev/sda6                9845M     8235M     1110M  89% /media/disk   Note so for /, it says there are 9845M total; and Used 8960M - then remaining would be 9845-8960 = 885 M, however, here I have only 385M Available.  Also, for /media/disk, it says total 9845M, Used 8235M - then remaining would be 9845-8235 = 1610, however, here I have only 1110M Available.  In both cases, there is exactly 500 MB difference.  Where did this difference come from - and can I reclaim it?  Here is also lsof | grep 'deleted' - can't see nothing suspicious here:  $ lsof | grep 'deleted' nautilus  1911 user   21u      REG        8,5   142760     260562 /home/user/.local/share/gvfs-metadata/home (deleted) nautilus  1911 user   22w      REG        8,5    32768     268807 /home/user/.local/share/gvfs-metadata/home-fe882154.log (deleted) python    1919 user    8u      REG        8,5     4096     392258 /tmp/ffiqRK968 (deleted) python    2165 user    5w      REG        8,5        0     132261 /home/user/.[SNIP].lock (deleted) python    2166 user    5w      REG        8,5        0     132261 /home/user/.[SNIP].lock (deleted) python    2185 user   21r      REG        8,5   142760     260562 /home/user/.local/share/gvfs-metadata/home (deleted) python    2185 user   22r      REG        8,5    32768     268807 /home/user/.local/share/gvfs-metadata/home-fe882154.log (deleted) gnome-ter 2279 user   27u      REG        8,5      640     392575 /tmp/vte5KDX2X (deleted) gnome-ter 2279 user   28u      REG        8,5     4936     392605 /tmp/vteKRDX2X (deleted) gnome-ter 2279 user   29u      REG        8,5      648     392947 /tmp/vteMZDX2X (deleted) ubuntuone 2544 user   17u      REG        8,5     4096     392335 /tmp/ffiMErq0V (deleted) bamfdaemo 3235 user   12r      REG        8,5   143868     269077 /home/user/.local/share/gvfs-metadata/root (deleted) bamfdaemo 3235 user   13r      REG        8,5    32768     272310 /home/user/.local/share/gvfs-metadata/root-18092a02.log (deleted) firefox   5291 user   59u      REG        8,5    33288     132262 /var/tmp/etilqs_YdeZiWSd5iQwJ4U (deleted) firefox   5291 user   60w      REG        8,5    32768     132271 /var/tmp/etilqs_MNLXhEaEqoXMm9b (deleted) firefox   5291 user   70u      REG        8,5    34952     132297 /var/tmp/etilqs_yXDdwVeMxmmdpNz (deleted)
116899
On my Amazing 2GB EeePC Surf, I have no more space left!  This is quite normal, and it happens every now and then. Just delete a few large, unneeded files and everything should be good, right?  So I go and find a 2MB file in /tmp, and rm -rf it. Check free space again, and -- still nothing?!  I had to remove about 30MB of files before it registered some free space.  Now, my question is, what's up with this strange behaviour?
111897
I put my program in startup applications because of this. The directory /var/log is taking around 36 GB space.   Can I delete syslog and syslog.1 file which are taking the highest percentage of storage in /var/log directory?
93366
I've got my mom's computer running Ubuntu 12.04 LTS. It's been working just fine but all of the sudden syslog has been filling up. And by filling up I mean I just deleted a /var/log/syslog that was 400GB in size. Yes - Gigabytes.  While I'm sure there was some useful information in there, I'm not sure that 400GB is any kind of information to sift through. And what's really amazing about it is that it happened within a period of 8 hours - I had ran df around noon, and between then and now her drive filled up 30% (from just under 70% to 100%).  What could be causing this and how could I fix it?`  EDIT Looks like the usb is the offender:  Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157829] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157836] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157842] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157849] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157857] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157863] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157870] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157877] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157884] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use Sep  8 08:52:10 pamela-desktop kernel: [ 6198.157891] usb 1-3: usbfs: process 1500 (demond_nscan) did not claim interface 3 before use
85731
I was running out of /tmp space on one of my servers today so I attached a new 100GB disk to the system and did the following without unmounting /usr/tmpDSK from /tmp:  mkfs.ext4 /dev/xvde mount /dev/xvde /tmp   and now df -h outputs as:  Filesystem      Size  Used Avail Use% Mounted on /usr/tmpDSK      98G  4.5G   89G   5% /tmp /dev/xvde        98G  4.5G   89G   5% /tmp    The size of /usr/tmpDSK shows :  [root@server2 usr]# ll -h /usr/tmpDSK -rw------- 1 root root 2.3G Jan 27 17:32 /usr/tmpDSK    Different forums suggested using mhddfs to mount multiple drives on a single mount point, but I just did it directly and it seems to have worked -- or am I missing something?  I am hoping to better understand what actually happened.
55442
While creating a 250GiB backup partition for my data, I have noticed lots of discrepancies between reported partition size and free space in Nautilus, gParted, df, tune2fs, etc.  At first I thought it was a GiB / GB confusion. It was not.  Then I thought it could be ext4's reserved blocks. It was not.  Im completely puzzled. Here are some images. Here are the steps:   First, NTFS. 524288000 sectors x 512 bytes/sector = 268435456000 bytes = 268.4 GB = 250 GiB.      Nautilus say "Total Capacity: 250.0 GB" (even though its actually GiB, not GB). Apart from that minor mislabeling, so far, so good   Now, same partition, formated as ext4 with gparted:     First, Last and Total sectors are the same. It IS the same 250GiB partition. Used size is 4.11GiB (reserved blocks maybe?)    Nope. Looks like reserved blocks are 12.7 GiB (~5%. ouch!). But... why Total Capacity is now only 246.1 GiB ???. That difference (sort of) matches the 4.11 GiB reported by gparted. But... if its not from reserved blocks, what is it? And why gparted didnt report that 12.7GiB of used space?  $ df -h /dev/sda5 Filesystem            Size  Used Avail Use% Mounted on /dev/sda5             247G  188M  234G   1% /media/BACKUP   df matches Nautilus in reported free space. But.. only 188M used? Shouldnt it be ~12GB? And total capacity is still wrong. So i ran tune2fs to find some clues. (irrelevant output is ommited)  $ sudo tune2fs -l /dev/sda5 tune2fs 1.41.12 (17-May-2010) Filesystem volume name:   BACKUP Filesystem UUID:          613d592e-47f5-4206-96a7-210090d340ef Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags:         signed_directory_hash  Filesystem state:         clean Filesystem OS type:       Linux Block count:              65536000 Reserved block count:     3276800 Free blocks:              64459851 First block:              0 Block size:               4096   65536000 total blocks * 4096 bytes/block = 268435456000 bytes = 268.4 GB = 250 GiB. It matches gparted.  3276800 reserved blocks = 13421772800 bytes = 13.4 GB = 12.5 GiB. It (again, sort of) matches Nautilus.  64459851 free blocks = 264027549696 bytes = 264.0 GB = 245.9 GiB. Why? Shouldnt it be either 250-12.5 = 237.5 (or 250-(12.5+4.11)=~233) ?  Removing reserved blocks:  $ sudo tune2fs -m 0 /dev/sda5 tune2fs 1.41.12 (17-May-2010) Setting reserved blocks percentage to 0% (0 blocks)  $ sudo tune2fs -l /dev/sda5 tune2fs 1.41.12 (17-May-2010) Filesystem volume name:   BACKUP Filesystem UUID:          613d592e-47f5-4206-96a7-210090d340ef Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags:         signed_directory_hash  Filesystem state:         clean Filesystem OS type:       Linux Block count:              65536000 Reserved block count:     0 Free blocks:              64459851 Block size:               4096   As expected, same block count, 0 reserved blocks, but... same free blocks? Didnt I just freed 12.5 GiB ?  $ df -h /dev/sda5 Filesystem            Size  Used Avail Use% Mounted on /dev/sda5             247G  188M  246G   1% /media/BACKUP     Looks like I did. Avaliable space went up from 233 to 245.9 GiB. gparted didnt care at all, showing exactly same info! (useless to post an identical screenshot)  What a huge mess!  I tried to document it as best as I could... So, please can someone give me any clue on what's going on here?   What are those misterious 4.11 GiB missing from NTFS -> ext4 formatting? Why there are so many discrepancies between gparted, Nautilus, tune2fs, df? What is wrong with my math? (questions in bold scattered this post)   Any help is appreciated. While I can not figure what is going on, I am serilously considering giving up on ext4 in favor of NTFS for everything but my / partition.  Thanks!
49231
Why don't I have this option?    here's my disk layout  sudo fdisk -l  Disk /dev/sda: 640.1 GB, 640135028736 bytes 255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x5b53cc54     Device Boot      Start         End      Blocks   Id  System /dev/sda1   *        2048      409599      203776    7  HPFS/NTFS/exFAT /dev/sda2          409600  1153767021   576678711    7  HPFS/NTFS/exFAT /dev/sda3      1216962560  1250050047    16543744    7  HPFS/NTFS/exFAT /dev/sda4      1250050048  1250261679      105816    c  W95 FAT32 (LBA)  Disk /dev/sdb: 4005 MB, 4005527552 bytes 32 heads, 63 sectors/track, 3880 cylinders, total 7823296 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x20d8782d     Device Boot      Start         End      Blocks   Id  System /dev/sdb1   *          63     7822079     3911008+   c  W95 FAT32 (LBA)
108469
I'm running Linux Mint 14 Nadia.  The Linux partition has 10G.  When the system starts, du reports 80% usage.  Then the usage slowly grows until it reaches 100% and the system becomes unusable.  (It can happen on the order of days or weeks).  After the reboot the usage resets to 80%.  The strangest thing of all is that du shows no change.    Here's output of those commands (Windows and external drive partitions are elided):  # --- Just after reboot ---  $ df -h      Filesystem      Size  Used Avail Use% Mounted on /dev/sda1       9.8G  7.3G  2.0G  80% / none            4.0K     0  4.0K   0% /sys/fs/cgroup udev            428M  292K  428M   1% /dev tmpfs            88M  1.3M   87M   2% /run none            5.0M     0  5.0M   0% /run/lock none            437M  288K  437M   1% /run/shm none            100M   12K  100M   1% /run/user  $ sudo du -x   -d1 -h / 186M    /opt 512M    /var 11M /sbin 556K    /root 1.3G    /home 613M    /lib 8.0K    /media 4.6G    /usr 16K /lost+found 111M    /boot 39M /etc 4.0K    /mnt 60K /tmp 9.1M    /bin 4.0K    /srv 7.3G    /            # &lt;-- note this   # --- After some time ---  $ df -h Filesystem      Size  Used Avail Use% Mounted on /dev/sda1       9.8G  9.1G  199M  98% / none            4.0K     0  4.0K   0% /sys/fs/cgroup udev            428M  292K  428M   1% /dev tmpfs            88M  1.3M   87M   2% /run none            5.0M     0  5.0M   0% /run/lock none            437M   27M  411M   7% /run/shm none            100M   28K  100M   1% /run/user  $  sudo du -x   -d1 -h / 186M    /opt 511M    /var 11M /sbin 556K    /root 1.4G    /home 613M    /lib 8.0K    /media 4.6G    /usr 16K /lost+found 111M    /boot 39M /etc 4.0K    /mnt 520K    /tmp 9.1M    /bin 4.0K    /srv 7.3G    /              # &lt;-- note this   (Note: I use hibernation.  After the hibernation, the usage stays the same, and after reboot, it resets to 80%.)  How do I track what eats the space?  I've read .  I'm still in the dark.  How do I find out which program is responsible for this behavior?  After edit: found it.  The space is claimed by the kernel log, which is seen by dmesg.  It fills up because my machine generates errors at the rate 5 a second.  (It's related to .)  Let the future readers with a similar problem - slowly-filling disk space unseen by du - not forget to try dmesg in searching for the cause.
6571
I am trying to understand how to see the total size of my hard drive &amp; how much is left. It was recommended on various searches to use the command below   df -h Filesystem      Size  Used Avail Use% Mounted on udev            7.8G     0  7.8G   0% /dev tmpfs           1.6G  9.6M  1.6G   1% /run /dev/sda1       219G   29G  180G  14% / tmpfs           7.8G   18M  7.8G   1% /dev/shm tmpfs           5.0M  4.0K  5.0M   1% /run/lock tmpfs           7.8G     0  7.8G   0% /sys/fs/cgroup cgmfs           100K     0  100K   0% /run/cgmanager/fs tmpfs           1.6G   64K  1.6G   1% /run/user/1000   However I don't understand any of these directories. I mean what are they, are these all directories or partitions or what? And why do they appear under "mounted on"? How does that bit work. I assume the /dev/sda1 is my solid state drive? So now if I install applications, which one of these directories does my software get installed  into? I assume it just gets installs in the / directory (I haven't even got a clue what the / directory is). Can someone explain what the other directories are and what they are used for?
94972
I am getting a 50% larger "Size on Disk" than the "Size" of files would lead me to expect, as linked. I have some idea from other posts that I have read about cluster size and small file allocation to clusters causing waste but would that account for 300GB extra space used/wasted?    Any ideas on how I could resolve this disparity and reduce the Size on Disk please?
79900
I've tried to deal with this for days now with no luck. In this forum and also in other ones I can see a lot of discussion about this but none of the solutions have worked for me.  My current situation is that I've got some GBs "missing" that I can't free or find anywhere. I guess this is some kind of problem like memory leaks that only get fixed when rebooting, but I just would like to ask if someone has a better idea because there are currently a few customers on that server.  Here are some of the commands I've seen in other threads and my particular outputs:  df -h  Filesystem            Size  Used Avail Use% Mounted on /dev/sda1              19G   16G  1.8G  90% / tmpfs                 384M     0  384M   0% /lib/init/rw udev                   10M  1.2M  8.9M  12% /dev tmpfs                 384M     0  384M   0% /dev/shm   du -Pshx /* 2>/dev/null  4.8M    /bin 27M /boot 0   /cdrom 1.2M    /dev 8.8M    /emul 504M    /etc 4.0K    /grubconf 88K /home 60K /images 0   /initrd.img 147M    /lib 0   /lib32 0   /lib64 16K /lost+found 12K /media 4.0K    /mnt 4.4M    /opt 777M    /proc 57M /root 4.7M    /sbin 4.0K    /selinux 4.0K    /srv 0   /sys 4.0K    /tmp 332M    /usr 471M    /var 0   /vmlinuz   lsof +L1  (no output)   lsof | grep -i delete  (no output)   find / -size +50000 -exec ls -lah {} +;  -r-------- 1 root    root 777M 2015-07-21 06:19 /proc/kcore -rw------- 1 root    root  64M 2015-07-09 03:31 /sys/devices/pci0000:00/0000:00:06.0/0000:01:04.0/resource0 -rw-r----- 1 root    adm   49M 2015-07-21 06:19 /var/log/auth.log -rw-r----- 1 root    adm  174M 2015-07-19 06:25 /var/log/auth.log.1 -rw-rw---- 1 control mail 100M 2015-07-21 06:00 /var/mail/control   If you make the maths from du, for example, you get a few GBs, but nothing close to 16GB.  / is ext3.  OS is Debian 6.0  is there anything am I missing here?
103581
Please suggest me any particular unnecessary file that I can clean to back everything to normal condition(temporarily). (i.e. any log or archieve or anything ). My var/log has only 40MB and Home directory has 3GB of space(so I believe that's not a problem). Other than that what I can clean up to make space.   [user@host]$ df -h Filesystem            Size  Used Avail Use% Mounted on /dev/mapper/vg_inamivm-lv_root                        18G   17G     0 100% / tmpfs                 1.9G     0  1.9G   0% /dev/shm /dev/sda1             485M   71M  389M  16% /boot   I am in a debian machine.   UPDATE1:  output of  cd /; du -sxh *  6.1M    bin 61M     boot 156K    dev 22M        etc 3.3G    home 306M    lib 18M     lib64 16K     lost+found 4.0K    media 4.0K    mnt 408K    opt du: cannot access `proc/18605/task/18605/fd/4': No such file or directory du: cannot access `proc/18605/task/18605/fdinfo/4': No such file or directory du: cannot access `proc/18605/fd/4': No such file or directory du: cannot access `proc/18605/fdinfo/4': No such file or directory 0       proc 208K    root 9.7M    sbin 0       selinux 4.0K    srv 0       sys 8.0K    tmp 536M    usr 187M    var   Update2  Output of ls -la /  dr-xr-xr-x.  22 root root  4096 Aug  7 08:42 . dr-xr-xr-x.  22 root root  4096 Aug  7 08:42 .. -rw-r--r--.   1 root root     0 Aug  7 08:42 .autofsck dr-xr-xr-x.   2 root root  4096 Mar 28 16:53 bin dr-xr-xr-x.   5 root root  1024 Mar 28 16:54 boot drwxr-xr-x.  16 root root  3580 Sep  9 03:13 dev drwxr-xr-x.  69 root root  4096 Aug 23 09:19 etc drwxr-xr-x.   9 root root  4096 Jun 29 16:10 home dr-xr-xr-x.   8 root root  4096 Mar  7  2012 lib dr-xr-xr-x.   9 root root 12288 Mar 28 16:53 lib64 drwx------.   2 root root 16384 Mar  7  2012 lost+found drwxr-xr-x.   2 root root  4096 Sep 23  2011 media drwxr-xr-x.   2 root root  4096 Sep 23  2011 mnt drwxr-xr-x.   3 root root  4096 Mar  7  2012 opt dr-xr-xr-x. 355 root root     0 Aug  7 08:42 proc dr-xr-x---.   5 root root  4096 Aug 17 18:27 root dr-xr-xr-x.   2 root root  4096 May  2 09:13 sbin drwxr-xr-x.   7 root root     0 Aug  7 08:42 selinux drwxr-xr-x.   2 root root  4096 Sep 23  2011 srv drwxr-xr-x.  13 root root     0 Aug  7 08:42 sys drwxrwxrwt.   3 root root  4096 Sep 13 03:37 tmp drwxr-xr-x.  13 root root  4096 Mar 28 17:53 usr drwxr-xr-x.  18 root root  4096 Mar  7  2012 var
116431
What sets the size of the tmpfs? (On my machine it resides in /dev/shm) I can see its entry in /etc/fstab, but no notation of its size. When checking with df -h, it seems to be half the size of the physical memory installed in the system. Is this the default behavior?  Also, what happens if it gets full? Does it expand dynamically forcing other running programs into swap? Does tmpfs itself moves into swap partition?   Finally, what takes priority into the memory tmpfs or applications? i.e., if I have tmpfs sufficiently full (like 40% of the physical memory) and I have programs that requires 70% of the physical memory, which one gets the priority?
34705
I used du to list all folders and sort by size, the results simply doesn't add up to how much disk space is used(using df). There's about 20G in discrepency, why?   [root@xxx lib]# du --max-depth=1 -h /| sort -n -r 310M    /lib 123M    /root 96K /dev 88M /etc 75G / 73G /var 30M /sbin 20M /boot 20K /tmp 18M /lib64 16K /mnt 16K /lost+found 12K /home 8.0K    /srv 8.0K    /selinux 8.0K    /opt 8.0K    /misc 8.0K    /media 7.0M    /bin 1.2G    /usr 0   /sys 0   /proc [root@xxx lib]# df -h Filesystem            Size  Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00                       298G   94G  189G  34% / /dev/sda1              99M   26M   69M  28% /boot tmpfs                 2.0G     0  2.0G   0% /dev/shm
29969
When I'm using the command "df -h" I'm having the following output :   Filesystem                 Size   Used  Avail Use% Mounted on /dev/mapper/fedora-root    20G    9,4G  8,8G  52% / devtmpfs                  1,9G       0  1,9G   0% /dev tmpfs                     1,9G    1,2M  1,9G   1% /dev/shm tmpfs                     1,9G    1,0M  1,9G   1% /run tmpfs                     1,9G       0  1,9G   0% /sys/fs/cgroup tmpfs                     1,9G    108K  1,9G   1% /tmp /dev/sda1                 477M    129M  319M  29% /boot /dev/mapper/fedora-home   916G    279G  591G  33% /home   Or it says my root is of 20G with 9.4 used and 8.8 still available it's 2G that disappeared. I know a very similar question as been answered here  and I'm just wondering if the reason could be the same here since I'm using LVM.  If not is there any way to reclaim that space that disappeared because for home there is an amazing 46G that disappeared.
81410
I'm trying to copy a file to a USB flash drive. The drive does not have a write-protect switch.  df gives the following:  $ df -h . Filesystem      Size  Used Avail Use% Mounted on /dev/sde1       1.9G  622M  1.3G  33% /media/lindenb/803C-078D   df -i produces strange output to me (0 everywhere)  $ df -i . Filesystem     Inodes IUsed IFree IUse% Mounted on /dev/sde1           0     0     0     - /media/lindenb/803C-078D   Number of files on the drive:  $ find . |wc -l 170   But when I try to copy a file, I get this:  $ mv ~/file.txt ./ mv: cannot create regular file ‘./file.txt’: No space left on device   How can I fix this ?
17740
I have Lubuntu 16.10 installed on my disk mounted as /.  The problem is that the CUPS log file( /var/log/cups/error.log)  grows all the time until I no have free space left on the disk...   So when I delete that file, the space on disk freed up again  I already tried:    fsck disk usage analyzer every apt-cleaning/autocleaning, and dependencies fixing.    How should I proceed?  du -sxh:  9,0G    .  Model: ATA ST3160815AS (scsi) Disk /dev/sda: 160GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags:   Number  Start   End     Size    Type      File system     Flags  1      32,3kB  50,3GB  50,3GB  primary   ext4            boot  2      50,3GB  160GB   110GB   extended  5      50,3GB  158GB   108GB   logical   ext4  6      158GB   160GB   2136MB  logical   linux-swap(v1)   parted --list &amp;&amp; sudo df -h:  Model: ATA ST3160815AS (scsi) Disk /dev/sda: 160GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags:   Number  Start   End     Size    Type     File system  Flags  1      32,3kB  50,3GB  50,3GB  primary  ext4         boot  2      50,3GB  160GB   110GB   primary  ext4   Filesystem      Size  Used Avail Use% Mounted on udev            985M     0  985M   0% /dev tmpfs           201M  6,3M  195M   4% /run /dev/sda1        46G   43G  709M  99% / tmpfs          1003M  188K 1003M   1% /dev/shm tmpfs           5,0M  4,0K  5,0M   1% /run/lock tmpfs          1003M     0 1003M   0% /sys/fs/cgroup tmpfs           201M   36K  201M   1% /run/user/1000 /dev/sda2       101G   60M   96G   1% /media/aram/
49630
I written an ISO image to my hard disk using sudo dd if=image.iso of=/dev/sda. I meant /dev/sdc, and now running sudo fdisk -l returns only one partition on /dev/sda while there is supposed to be 6. Is it possible to recover my data?  I didn't shut down (reboot) my computer yet.