Sponsored Content
Full Discussion: Reclaim deleted disk space
Top Forums UNIX for Dummies Questions & Answers Reclaim deleted disk space Post 302391733 by methyl on Tuesday 2nd of February 2010 10:15:18 AM
Old 02-02-2010
/var is a separate mountpoint according to your post. Deleting files in /var/adm will not affect free space in the root filesystem.
Try looking under the root filesystem bearing in mind that yours is 50 Gb larger than a normal system and no doubt contains something more than just unix ! Be careful and take local advice before deleting anything.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to keep white space is being deleted using read

I am using Posix shell to write a script. The problem I am having is that when I use the read command to go through a file I lose the tabs. How can I keep this from happening? (1 Reply)
Discussion started by: keelba
1 Replies

2. UNIX for Dummies Questions & Answers

available disk space on disk device???

Hello, Can someone please tell me which command to use to determine the available disk space on a given disk device? I have to write a shell script that compresses files and stores them in a specific location but I am not sure how "conservative" I should be? Thanks in advance! Al. (4 Replies)
Discussion started by: alan
4 Replies

3. Filesystems, Disks and Memory

disk space

Hello All- Am new member to this forum. Have some unix experience. But true believer in it compared to windows. Have a question regarding the disk space. I know a command to check the total disk space utilization using: df -k . but what is the command to check the same disk space by... (6 Replies)
Discussion started by: milkyway
6 Replies

4. Shell Programming and Scripting

Disk Space

Hi This is my script for disk space monitoring clear if then echo "You must be root user to execute the script" fi ALERT_LEVEL=10 CONSUMPTION_LEVEL= `df -k | awk {'print $5'} | cut -d '%' -f1 | sed "1 d"` for i in $CONSUMPTION_LEVEL do FILE_SYSTEM=`df -k | awk {'print $1'} |... (3 Replies)
Discussion started by: chrs0302
3 Replies

5. Red Hat

disk space

when i check /export directory of my machine gets filled up (85%) i removed some old logs. but after cleaning df -k command still shows that /export is still 85% full. Is there a way to force df to reflect actual free space without rebooting? My machine is a production one and can't... (8 Replies)
Discussion started by: aboorkuma
8 Replies

6. Linux

How to reclaim the space which i used to increse the swap space on Xen,

Hi, i have done a blunder here, i increased the swap space on Xen5.6 server machine using below steps :- 1056 dd if=/dev/zero of=/root/myswapfile bs=1M count=1024 1057 ls -l /root/myswapfile 1058 chmod 600 /root/myswapfile 1059 mkswap /root/myswapfile 1060 swapon /root/myswapfile ... (1 Reply)
Discussion started by: apm
1 Replies

7. Shell Programming and Scripting

How to reallocate the deleted logfile space?

Hi All, I know this is a simple question but i am not sure the exact answer it. Here is the question: There is a huge log file , if we delete the log file ,how the corresponding occupied file memory relocate to Hard Disk. Thanks Srinivas (3 Replies)
Discussion started by: Srinivas Gadi
3 Replies

8. Red Hat

Files not getting deleted with rm & occupying space in filesystem

Hello, OS version is Red Hat Enterprise Linux Server release 6.5 (Santiago). In one of the filesystem some old files post clone are not getting removed even with 'rm' # ls -ltr | grep meagpd_62.dbf -rw-rw---- 1 oracle oinstall 34358697984 Sep 1 08:46 meagpd_62.dbf # rm... (7 Replies)
Discussion started by: saharookiedba
7 Replies

9. UNIX for Beginners Questions & Answers

CentOS 6 ran out of space, need to reclaim it

Hello everyone, I am having an issue here with CentOS release 6.6 (Final) that shows all of the space used up, but I can't tell where the space went. Seemingly I am using up 100%, according to df -h Filesystem Size Used Avail Use% Mounted on... (27 Replies)
Discussion started by: DannyBoyCentOS
27 Replies

10. UNIX for Beginners Questions & Answers

Safe way to shrink lvm vg_*-lv_swap partition and reclaim freed space on Linux?

Hello, # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sr0 11:0 1 1024M 0 rom sda 8:0 0 38.2G 0 disk ├─sda1 8:1 0 500M 0 part /boot └─sda2 8:2 ... (2 Replies)
Discussion started by: centosadmin
2 Replies
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 12:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy