08-27-2019
The main problem with putting all the data on the same root partition when running a production database is that if the database directory gets very large and fills up the root partition, it is possible the system will not boot and / or critical root partition log files will not log.
When running databases like we do with very large binary transactions logs, the database directory gets very large very fast.
However, when on a separate partition and full, not on root, the system will boot and continue to log (syslog, etc).
That is a big plus for most system admins knowing that a full data partition will not crash the boot partition.
For me, it's nothing to do with "traditional unix".. I do it because I do not want a full db partition to effect the boot partition and since I have seen this problem many times, it's better to have the db crash than the entire system / server crash.. I can log into a crash due to a full db partition, but I cannot login to a system which will not boot due to a full root / boot partition.
So, for me, all my data for a big database is off the root / boot partition, always (for production). Same is true for my backup directory of mysql dumps.
(As Peasant says as well in his analysis ...)
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
hi,
I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u.
The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
Discussion started by: Martyn
2 Replies
2. Shell Programming and Scripting
can we come to know all the command ran bya user for last 1 day (1 Reply)
Discussion started by: narang.mohit
1 Replies
3. UNIX for Dummies Questions & Answers
I have a disk space issue on one of my unix servers.
it is showing 98% full.. i found the offending folder and removed it. but i have not reclaimed the disk space.
is there another command that i need ?
thank you in advance for any assistance. (4 Replies)
Discussion started by: JanSP
4 Replies
4. Shell Programming and Scripting
Recently I was on an operational call and heard the people running my code placing the code in the /tmp directory and running as root. I had not planned on that. So I want to add some checks to my code (using ksh93):
# ---------- ---------- ----------
# root not allowed to run this
#... (3 Replies)
Discussion started by: ericdp63
3 Replies
5. Shell Programming and Scripting
Hi, I have written a script and placed in an application and the script can be executed manually only. But somehow one of the method in the script is being called and bringing the application down. But we are not able to find any instance of script running.
Is there a way to findout whether the... (1 Reply)
Discussion started by: Satyak
1 Replies
6. Linux
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. Red Hat
Hi. My "/usr" folder is running out of space. My "/home" folder is quite large and has a lot of free space. As follows:
Filesystem Type Size Used Avail Use% Mounted on
...
/dev/sda5 ext3 9.7G 2.6G 6.7G 28% /
/dev/sda7 ext3 152G 16G 128G 11% /home
/dev/sda3 ... (7 Replies)
Discussion started by: pkiula
7 Replies
8. Red Hat
Dear Linux Experts,
On my windows 7 desktop with the help of Vmware workstation (Version 7.1),
created virtual machine and installed Centos 5.7 successfully using ISO image.
Query : Is this possible to upgrade the Centos 5.7 using Centos 5.8 ISO image to Centos version 5.8?.. if yes kindly... (2 Replies)
Discussion started by: Ananthcn
2 Replies
9. AIX
Hello
I recently received a request to reclaim hard disks and IP addresses within an AIX system(s). THe file systems are no longer in use and the client has indicated that it is OK to remove them and reclaim the disks and release the IP's. Now, since the file systems belong to a Volume group I... (8 Replies)
Discussion started by: Joseph Sabo
8 Replies
10. UNIX for Beginners Questions & Answers
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
LEARN ABOUT FREEBSD
gptboot
GPTBOOT(8) BSD System Manager's Manual GPTBOOT(8)
NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers
DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par-
tition with gpart(8).
IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less.
PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions.
bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each
one until successful.
bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme
attribute. Multiple partitions may have the bootonce and bootme attributes set.
bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by
the system. See BOOTING and POST-BOOT ACTIONS below for details.
USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition
found.
The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is
left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on
that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files.
After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition
becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system
attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system
that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions
with bootme attributes are found, booting will be attempted from the first UFS partition found.
BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set
to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and
bootonce attributes set on those partitions.
bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each
partition, the bootme attribute is removed and the boot attempted.
bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute.
If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk.
POST-BOOT ACTIONS
The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed
attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that
successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions.
The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these.
FILES
/boot/gptboot bootcode binary
/boot.config parameters for the boot blocks (optional)
EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically
installed in combination with gptboot.
Install gptboot on the ada0 drive:
gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
gptboot can also be installed without the PMBR:
gpart bootcode -p /boot/gptboot -i 1 ada0
Set the bootme attribute for partition 2:
gpart set -a bootme -i 2 ada0
Set the bootonce attribute for partition 2, automatically also setting the bootme attribute:
gpart set -a bootonce -i 2 ada0
SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8)
HISTORY
gptboot appeared in FreeBSD 7.1.
AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>.
BSD
February 5, 2014 BSD