Re: [Dorset] Full Root Partition
Thanks to David and Ralph, now able to get into the laptop and to prove it this reply is from laptop. David you were right files were in the trash folder and hence partition not 'cleared'. From live disk checked 'Trash' and deleted the backup which showed all files copied to root. Now / is only using 22% of space. Many thanks for quick fix! Knew I could rely on DLUG list. C A Wills /Supporting Linux & Open Source/ // On 19/01/15 17:48, David Wilkinson wrote: Hi Clive, How did you remove the backup? If it was via the GUI then I suspect it has gone in to the trash folder. ( ~/.local/share/Trash) The other possibility is that the changes didn't write to the hard drive, If the backup files are still there then after removing them issue a "sync" command in to a terminal to make sure the changes are flushed out to the disk. Regards David On 19/01/15 17:31, Clive Wills wrote: Hi All Just clearing out my 'Home' folder on laptop and copying it to a separate disk all OK. So decided to 'Back-up' the 'Home' folder onto the NAS drive using Lucky Backup on my Mint 16 system. (Lucky Backup is a graphical front end to Rsync) Did a verification run to check if all OK and it was; so pressed Backup and watched it run through the Home folder, it got to within the last few files then reported something like "/ file system full, operation terminated"!! Had to run from a 'Live' disk to see what happened as the NAS drive is a 2Tb drive. It would appear that the backup was saved to the laptop's /root partition (System partition) not the NAS! No wonder it was full as the root partition was only 27Gb and the backup was larger than that. Using the 'Live' disk I thought I'd removed (deleted) the backup file from / hoping to free up space and then re-booted. Still reports system full and looking, via Gparted, at that partition - it's still showing full? On re-booting laptop reports quote:- "MDM could not write a new authorisation entry to disk. Possibly out of diskspace. Error: No space left on device". Terminal quote then carries on with:- [ 54.4015821 sd 6:o:o:o: [sdb] Asking for cache data failed. [ 54.4016501 sd 6:o:o:o: [sdb] Assuming drive cache: write through. [ 106.1986421 sd 6:o:o:o: [sdb] Asking for cache data failed. This then carries on and nothing can be done. Why does it not accept that the large file has been deleted and still shows partition full? How can I recover that partitions empty space? and get entry to the system. I thought that deleting the file from a live system would have given enough space back to carry on booting in. Clive -- Next meeting: Bournemouth, Tuesday, 2015-02-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Full Root Partition
Hi Clive, David wrote: > How did you remove the backup? If it was via the GUI then I suspect > it has gone in to the trash folder. ( ~/.local/share/Trash) That would be my guess. Open a terminal from the Live boot, find and remove the file from that. Useful commands are cd dir -- change working directory to dir pwd -- print working directory ls -- list files ls -l -- long listing, fifth field is file's extent in bytes df . -- disk free for filesystem containing working directory rm foo -- remove file foo, no recovery or getting it back find -name '*foo*' -- search from working directory down for that file Hopefully, you can find where the backup is now and remove it, df will show lots of space. If you find it, but can't remove it, a copy-and-paste of the terminal's contents with the problem would be helpful. Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday, 2015-02-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
Re: [Dorset] Full Root Partition
Hi Clive, How did you remove the backup? If it was via the GUI then I suspect it has gone in to the trash folder. ( ~/.local/share/Trash) The other possibility is that the changes didn't write to the hard drive, If the backup files are still there then after removing them issue a "sync" command in to a terminal to make sure the changes are flushed out to the disk. Regards David On 19/01/15 17:31, Clive Wills wrote: Hi All Just clearing out my 'Home' folder on laptop and copying it to a separate disk all OK. So decided to 'Back-up' the 'Home' folder onto the NAS drive using Lucky Backup on my Mint 16 system. (Lucky Backup is a graphical front end to Rsync) Did a verification run to check if all OK and it was; so pressed Backup and watched it run through the Home folder, it got to within the last few files then reported something like "/ file system full, operation terminated"!! Had to run from a 'Live' disk to see what happened as the NAS drive is a 2Tb drive. It would appear that the backup was saved to the laptop's /root partition (System partition) not the NAS! No wonder it was full as the root partition was only 27Gb and the backup was larger than that. Using the 'Live' disk I thought I'd removed (deleted) the backup file from / hoping to free up space and then re-booted. Still reports system full and looking, via Gparted, at that partition - it's still showing full? On re-booting laptop reports quote:- "MDM could not write a new authorisation entry to disk. Possibly out of diskspace. Error: No space left on device". Terminal quote then carries on with:- [ 54.4015821 sd 6:o:o:o: [sdb] Asking for cache data failed. [ 54.4016501 sd 6:o:o:o: [sdb] Assuming drive cache: write through. [ 106.1986421 sd 6:o:o:o: [sdb] Asking for cache data failed. This then carries on and nothing can be done. Why does it not accept that the large file has been deleted and still shows partition full? How can I recover that partitions empty space? and get entry to the system. I thought that deleting the file from a live system would have given enough space back to carry on booting in. Clive -- Next meeting: Bournemouth, Tuesday, 2015-02-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
[Dorset] Full Root Partition
Hi All Just clearing out my 'Home' folder on laptop and copying it to a separate disk all OK. So decided to 'Back-up' the 'Home' folder onto the NAS drive using Lucky Backup on my Mint 16 system. (Lucky Backup is a graphical front end to Rsync) Did a verification run to check if all OK and it was; so pressed Backup and watched it run through the Home folder, it got to within the last few files then reported something like "/ file system full, operation terminated"!! Had to run from a 'Live' disk to see what happened as the NAS drive is a 2Tb drive. It would appear that the backup was saved to the laptop's /root partition (System partition) not the NAS! No wonder it was full as the root partition was only 27Gb and the backup was larger than that. Using the 'Live' disk I thought I'd removed (deleted) the backup file from / hoping to free up space and then re-booted. Still reports system full and looking, via Gparted, at that partition - it's still showing full? On re-booting laptop reports quote:- "MDM could not write a new authorisation entry to disk. Possibly out of diskspace. Error: No space left on device". Terminal quote then carries on with:- [ 54.4015821 sd 6:o:o:o: [sdb] Asking for cache data failed. [ 54.4016501 sd 6:o:o:o: [sdb] Assuming drive cache: write through. [ 106.1986421 sd 6:o:o:o: [sdb] Asking for cache data failed. This then carries on and nothing can be done. Why does it not accept that the large file has been deleted and still shows partition full? How can I recover that partitions empty space? and get entry to the system. I thought that deleting the file from a live system would have given enough space back to carry on booting in. Clive -- Next meeting: Bournemouth, Tuesday, 2015-02-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread on mailing list: mailto:dorset@mailman.lug.org.uk How to Report Bugs Effectively: http://goo.gl/4Xue
