Root directory full, system does not boot Post: 302119530

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

root file system full

Hi I have a Solaris 2.5.1 system. Recently my file system is full and i couldn't find what flood my root file system. Anyone can suggext any directories i should look out for. I am using Samba and Patrol agent. I am just usng this server as a file server, users cannot login into the system,...

2. Solaris

Root file system is 82% full

Hi I want to find out the reason that why root partition is 82% full? when i did fu -k / then most of files were created on /var . can you please help me to find out what I need to do in order to find the reason. Regards Ajwat

3. UNIX for Dummies Questions & Answers

Root File System Full

Hi All, The root file system of the HP-UX serevr I use is showing as 100% full. It has a disk space of ~524MB. When I add up the sizes of all the files and directories (using du -sk) , except mount points, it came up to 237MB. But when I bdf it still shows 100% full Can anyone help...

4. Solaris

root directory is full

root directory in server / is full 100% , i already tried to delete any core file , log , .. still files under /proc directory take more than 4 G.. what you advice please i don't want to format the server and install again and re partition , i tried the FORMAT tools ! but it seems i cant do...

5. UNIX for Dummies Questions & Answers

Root file system full..Need help

Hi guys, In sun E250 server,root file system is full. we cleared log files in var/adm folder syslogs,mail logs,crash logs are empty. This is a production server. we are not able to run fsck from single user mode. I have given output of df and du command.How to create space in root...

6. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file...

7. UNIX for Advanced & Expert Users

Grub - how to boot a copy of Linux (full system backup)

Hi All, I have successfully backup & restore (using tar) one of my Debian Lenny Servers. On the restore server (standby machine), everytime i have to erase the disk & extract the tar backup. I want to extract the tar on the running restore server on a directory for e.g /systembackup-01,...

8. HP-UX

File system full, won't complete boot

Hello, I have a very old hp rp2450 running 11i2 that I had to power off. When turning it back on it hangs with the following message. Would booting into SUM get me any further? I've never used SUM, so I'm asking before I go down that rabbit hole. Thanks for the help. # ## extra content...

9. UNIX for Dummies Questions & Answers

[Solved] Boot Failure - Openindiana w/ Napp-it - Full Root?

Came home the other day to a Napp-it Gui that would not load. Login would appear but when i attempted I would get the following Set default permissions and reading disk and pool parameter, please wait.. in case of problems, try a reboot after Power-Off or check disk and pool status at CLI....

LEARN ABOUT SUNOS

systemd-volatile-root.service

SYSTEMD-VOLATILE-ROOT.SERVICE(8)			   systemd-volatile-root.service			  SYSTEMD-VOLATILE-ROOT.SERVICE(8)

NAME

       systemd-volatile-root.service, systemd-volatile-root - Make the root file system volatile

SYNOPSIS

       systemd-volatile-root.service

       /lib/systemd/systemd-volatile-root

DESCRIPTION

       systemd-volatile-root.service is a service that replaces the root directory with a volatile memory file system ("tmpfs"), mounting the
       original (non-volatile) /usr inside it read-only. This way, vendor data from /usr is available as usual, but all configuration data in
       /etc, all state data in /var and all other resources stored directly under the root directory are reset on boot and lost at shutdown,
       enabling fully stateless systems.

       This service is only enabled if full volatile mode is selected, for example by specifying "systemd.volatile=yes" on the kernel command
       line. This service runs only in the initial RAM disk ("initrd"), before the system transitions to the host's root directory. Note that this
       service is not used if "systemd.volatile=state" is used, as in that mode the root directory is non-volatile.

SEE ALSO

       systemd(1), systemd-fstab-generator(8), kernel-command-line(7)

systemd 237													  SYSTEMD-VOLATILE-ROOT.SERVICE(8)