search for: parititions

I am building three identical systems. Well they will have different host names, and with time the software setups will drift. But at install time they are identical. Is there some way, (with dd I might guess) to do a hardare level copy? All three drives are Hitachi DK23DA-40F (40Gb). Supposedly factory reconditioned (they are in sealed bags with a drive sticker stating: "Refurbished

I have a large disk full of data that I'd like to upgrade to SW RAID 1 with a minimum of downtime. Taking it offline for a day or more to rsync all the files over is a non-starter. Since I've mounted SW RAID1 drives directly with "mount -t ext3 /dev/sdX" it would seem possible to flip the process around, perhaps change the partition type with fdisk or parted, and remount as

...ot, /etc/rc.d/init.d/halt tries to umount all the filesystems (other than /proc, /, etc) but it fails on attempting to umount /var. I am pretty sure that this is because kjournald is using it. Does anyone have any suggestions as to how to deal with this? Should I just include /var in the list of parititions that are skipped on the first umount attempt? I have no particular reason to think this will work since the halt script will later proceed to attempt to remount everything in read-only mode which I expect to fail also. Any recommendations or admonishments would be appreciated, Shane

I'm putting the final touches on kinit, which is the user-space replacement (based on klibc) for the whole in-kernel root-mount complex. Pretty much the one thing remaining -- other than lots of testing -- is to handle automatically mounted md devices. In order to do that, without adding userspace versions of all the paritition code (which may be a future change, but a pretty big one)

I'm staring at the free CentOS images on AWS, and seeing that whoever set those up elected to use a partition for /dev/xvda1 rather than taking advantage of Amazon's tendency to use "/dev/xvda", "/dev/xvdb", etc. for each disk and use those directly as a file system. The result is that if you elect to allocate a larger base disk image, for example allocating 50 Gig to

Hi, Which is the recommended filesystem to be used for the bricks in glusterFS. ?? XFS/EXT3/EXT4 etc .???? Thanks & Regards, Bobby Jacob Senior Technical Systems Engineer | eGroup P SAVE TREES. Please don't print this e-mail unless you really need to. -------------- next part -------------- An HTML attachment was scrubbed... URL:

This is not really a problem at all. when you launch your image for the first time, you can specify a larger / volume size and cloud-init-tools will take care of the rest. This is well documented in the AWS userguides. -- Kelly Prescott On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote: > I'm staring at the free CentOS images on AWS, and seeing that whoever > set those up elected to use a

to follow-up, I will give an example. Here is the listing for the official centos AMI: IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen BLOCKDEVICEMAPPING EBS /dev/sda1

I want to put the document root for an application on a separate paritition that has more space. When I try to configure this I can't access the files in the new location. I've got the SELinux attributes set on the directory and its files, so I'm thinking it's something about the parent path that SELinux doesn't like, but I don't know where that's handled. My

...uration file with the CONFIG command, one can now also specify a new current directory with an APPEND statement. * Full ADV support for Syslinux, to boot-once and MENU SAVE works. * Full support of GPT-partitioned disks, including disks and/or parititions larger than 2 TiB (if supported by BIOS.) * The GPT handover protocol adjusted to the current T13 committee draft; see doc/gpt.txt. * HDT: code cleanup, small bugfixes * The "linux" syslinux installer (syslinux-nomtools) now has a command-line s...

I''ve got knee deep into learning how to use Opensolaris and zfs, and I see now that my goal of home zfs server may have been better served if I had partitioned the install disk leaving some of the 60GB to be added to a zpool. First, how much space does a working OS need. I don''t mean bare minimum but to be comfortable and have some growing room (on the install disk)?

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD

Hey all, I''m trying to figure out how to re-size physical partitions in the Dom U. I''ve read up what I can find on line and finally decided to have Logical Volumes in the Dom 0 and pass them as physical volumes for use in the Dom U. Here''s an example of what I''m doing. To start in the Dom 0 I created the LV''s with lvcreate -n guest_boot -L 100M

Okay, I'm going to ask the gajillion-dollar question... I've been doing syslinux for 11 years now. From a very limited scope it has since grown and is now a very advanced boot loader. Unfortunately, it's not clear to me anymore to what extent the work I'm doing is useful. I personally dislike grub because of its monolithic design, and because the grub people have

Wow, it takes a really long time to make a 2TB ext2fs. Are there better-than-default options that could be used for a large filesystem? mke2fs 1.34 (25-Jul-2003) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244203520 inodes, 488382016 blocks 24419100 blocks (5.00%) reserved for the super user First data block=0 14905 block groups 32768 blocks per group,

I'm running RH7.1 and Samba 2.2.2 . I would like to offer a VFAT partition on the server hard drive for universal read-write access. I mount the partition in fstab with /dev.hda5 /sys vfat defaults,rw,uid=1001,gid=1001 0 0 It mounts fine and shows up on the Windows 98 machine and can be opened. I can't write to it however. User and group 1001 are smbuser account, and they

Add the drivers/virt directory, which houses drivers that support virtualization environments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An

Add the drivers/virt directory, which houses drivers that support virtualization environments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An

Add the drivers/virt directory, which houses drivers that support virtualization environments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An

Add the drivers/virt directory, which houses drivers that support virtualization environments, and add the Freescale hypervisor management driver. The Freescale hypervisor management driver provides several services to drivers and applications related to the Freescale hypervisor: 1. An ioctl interface for querying and managing partitions 2. A file interface to reading incoming doorbells 3. An