Getting "E514: write Error (file system full ?)" error
location: linuxquestions.com - date: August 6, 2009
I am new to Linux operating system. I have installed Ubuntu in my laptop. I am getting the following error, when I try to create and write some content into the file in my home directory.
"E514: write Error (file system full ?)"
I am using ubuntu operating system in my laptop.
Note: I use Dual Booting system (Windows Vista and the Ubuntu)
I have made a new partition for this OS (18.5 Gb).
While installing the operating system, I have exported the windows folders.
so I believe this might have occupied all the memory. if it is so ho w to unexport the windows stuff.
write error (file system full?)
location: linuxquestions.com - date: February 10, 2005
I'm editing a document in vi, and when I try to save it, it says:
E514: write error (file system full?)
What's going on if I know the file system isn't anywhere near full? The machine is running Tomcat on Red Hat, and it's under load at the moment.
write error (file system full?) on fc 18 [closed]
location: linuxexchange.com - date: July 15, 2014
I'm not able to edit any file on my linux machine.
I checked the free space available on my system,
Filesystem Size Used Avail Use% Mounted on
devtmpfs 16G 0 16G 0% /dev
tmpfs 16G 84K 16G 1% /dev/shm
tmpfs 16G 18M 16G 1% /run
tmpfs 16G 0 16G 0% /sys/fs/cgroup
/dev/mapper/fedora-root 50G 4.9G 42G 11% /
tmpfs 16G 40K 16G 1% /tmp
/dev/mapper/fedora-home 428G 428G 0 100% /home
/dev/xvda1 477M 90M 358M 21% /boot
"/dev/mapper/fedora-home" is consuming complete memory, I'm not sure what this file signifies. How can I free the space consumed by this?
how to avoid "file system full" error message while copying/ ftping a file?
location: linuxquestions.com - date: January 27, 2012
copy command does it calculates the file size and the target available disc space?
is copy and ftp copy both same?
how to avoid "file system full" error message while copying/ ftping a file which is bigger than the target available disc space?
PCLOS: Boot error: file system type is ext2fs; partition is 0x83, and error 13
location: linuxquestions.com - date: September 22, 2008
I'm trying to complete the installation of PCLOS 2007 on a multiboot tower machine in which Grub is located in the Mandriva 2008.1 partition; windows is not installed. So, when I installed PCLOS, I chose to install its Grub in its own partition (hd2,5 or hdd6 [hdb is the CD-DVD drive]) with a chainload entry for it in Mandriva's menu.lst. During the installation, I reformatted that partition ext3. On trying to boot, I get this error:
file system type is ext2fs; partition is 0x83
error 13: Invalid or unsupported executable format
Google shows the error 13 message to mean the kernel image being loaded isn't recognized as Multiboot or one of the supported native formats, including Linux. However, the kernel is 22.214.171.124.tex5, exactly the same as the kernel in the successful PCLOS installation in my laptop.
Comparing the two installations, I noticed there was no /boot/grub/menu.lst file in the tower, but there was one in the laptop; I wrote up the same menu.l
Cannot write: Readonly file system (but rw in fstab)
location: ubuntuforums.com - date: July 22, 2008
This is not logical. My Ubuntu 6.10 server went like this some days ago, and now I cannot write to /dev/sda1 on mounted on/media2 (last line). This problem has come all of a sudden.
Any suggestions? /etc/mtab is all the same if you want to know.
I can though "fix" this by running "mount -a", and sda1 then becomes writeable..(why?)
/dev/sdb1 on / type ext3 (rw,errors=remount-ro,usrquota,grpquota)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sdb3 on /boot type ext3 (rw)
/dev/sdb4 on /home type ext3 (rw,usrquota,grpquota)
/dev/sda1 on /media2 type ext3 (rw)
Root File System Full /var/log/upstart/lightdm.log is 9.8 gb
location: ubuntuforums.com - date: May 23, 2013
When I booted this morning I got a Root File System Full notice and after snooping around I found that my /var/log/upstart/lightdm.log was 9.8 gb, which I suspect is the cause. Can I just delete this file? I think I should try to find out why it is so large, too. I have no idea how to do this. Thanks in advance for the help. I am running 12.04 with all updates installed.
Error splicing file: Readonly file system
location: ubuntuforums.com - date: January 13, 2013
SO, I was copying files onto a NEW 1tb Toshiba hard drive and suddenly get error
Error splicing file: Read-only file system
And the drive has vanished from Nautilus?
And gparted no longer sees sda drive?
I was copy 30gb in 3 separate files when this happened
dmesg shows tons of errors
[183065.875614] Buffer I/O error on device sda2, logical block 104612573
[183065.875616] Buffer I/O error on device sda2, logical block 104612574
[183065.875618] Buffer I/O error on device sda2, logical block 104612575
[183065.875620] Buffer I/O error on device sda2, logical block 104612576
[183065.875622] Buffer I/O error on device sda2, logical block 104612577
[183065.875623] Buffer I/O error on device sda2, logical block 104612578
[183065.875625] Buffer I/O error on device sda2, logical block 104612579
[183065.875627] Buffer I/O error on device sda2, logical block 104612580
[183065.875629] Buffer I/O error on device sda2, logical blo
File system NOT clean error
location: ubuntuforums.com - date: January 26, 2012
I have a dual boot laptop running Windows 7 and Ubuntu 11.10. The internal hard disk has 3 main partitions: 1 for Windows, 1 for Linux and 1 that I call New Volume for files I transfer between the two operating systems (mostly music and images). I also have a 1TB USB drive attached.
I installed a bunch of updates to Ubuntu 11.10 yesterday and this morning I can't write to my USB drive or to partition used for storing/swapping files; both mount as read only. In an effort to sort the problem I used Disk Utility to unmount the New Volume partition and checking the file system I get a message saying "file system NOT clean". Clicking the check and repair file system button again just crashes Disk Utility and I have no idea what to do to rectify the situation. Can anyone help?
I should add: I can read and write as normal when running Windows.
[SOLVED] An error occurred during the file system check. System unable to start
location: linuxquestions.com - date: June 21, 2011
I am having a problem while starting the Linux (RHEL 5.3).The system is unable to start. Following message is shown on the screen. Please take a look
Starting udev: [OK]
Loading default keymap(us): [OK]
Setting hostname rc [OK]
Setting up Logical Volume Management:7logical volume(s) in volume group VolGroup00 now active [OK]
/dev/VolGroup00/LogVol00: clean, 26960/7864320 files, 867567/7864320 blocks
/dev/VolGroup00/LogVol02: wxt3 recovery flag is clear, but journal has data.
/dev/VolGroup00/LogVol02: run journal anyway
/dev/VolGroup00/LogVol02: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY(i.e. , without a or p options)
/dev/VolGroup00/LogVol04: clean, 86
.. files, 280
/dev/VolGroup00/LogVol05: clean, 11/78
/dev/VolGroup00/LogVol01: clean, 11/78
/boot: clean, ../
*** An error occurred during the file system check.
Page: 1 2 3 4 5 6 7 8 9 10