search for: paritition

..., (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 to Hitachi Global Storage Technologies Specifications"). I would want to copy the paritition table and my 3 partitions (/boot, swap, LVM (/ and /home ext3 partitions in the LVM)) and all their contents. Thing is I only have one USB drive enclosure so I would be running from the drive I want to copy from. I would hope this is faster than 2 more installs.

...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 SW RAID1? I'm not trying to move over the O/S, just a data paritition with LOTS of data. So far, Google pounding has resulted in howtos like this one that's otherwise quite useful, but has a big "copy all your data over" step I'd like to skip: http://sysadmin.compxtreme.ro/how-to-migrate-a-single-disk-linux-system-to-software-raid1/ But it woul...

...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

...es 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) it would be good if the partition flag to auto-configure RAID was available in userspace, presumably through sysfs. Any feeling how best to do that? My current thinking is to export a "flags" entry in addition to the current...

...quot; parition and then use "resize2fs" to expand the "/" file system while the system is alive? Note that, because I'm a complete weasel, I know at least one way around this: add a second disk, copy the OS to *that*, set grub to boot from the second disk, reboot from that, paritition the first disk as desired, copy the OS back, reset grub to boot from the first disk, and pray. I've had good success with the approach in the past, and have rebuilt rougly 15,000 Linux systems this way. But the work predates CentOS, and I dont't want to go through that again. So, has anyon...

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:

...use > "resize2fs" to expand the "/" file system while the system is alive? > > Note that, because I'm a complete weasel, I know at least one way > around this: add a second disk, copy the OS to *that*, set grub to > boot from the second disk, reboot from that, paritition the first disk > as desired, copy the OS back, reset grub to boot from the first disk, > and pray. I've had good success with the approach in the past, and > have rebuilt rougly 15,000 Linux systems this way. But the work > predates CentOS, and I dont't want to go through that a...

...use > "resize2fs" to expand the "/" file system while the system is alive? > > Note that, because I'm a complete weasel, I know at least one way > around this: add a second disk, copy the OS to *that*, set grub to > boot from the second disk, reboot from that, paritition the first disk > as desired, copy the OS back, reset grub to boot from the first disk, > and pray. I've had good success with the approach in the past, and > have rebuilt rougly 15,000 Linux systems this way. But the work > predates CentOS, and I dont't want to go through that a...

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...

...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...

...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)? I''d like to paritition off however much that is, and create a partition of the rest to add to a zpool. I''m not going to be strapped for space really... but that will be at some future time. Right now I have a 60gb disk I installed osol-11 on, a 250gb IDE Disk that used to be on a windows XP machine. I also ha...

...Reading all physical volumes. This may take a while... No volume groups found No volume groups found And It continue to search the volume. SSD-RAID1 is a volume group on the dom0. A view of the dom0 partition : 2 SSD : -> RAID1 soft (md0) -> EXT4 /boot -> Luks Paritition -> LVM (PV : /dev/mapper/md1_crypt, VG : SSD-RAID1) -> /dev/SSD-RAID1/swap -> /dev/SSD-RAID1/root -> /dev/SSD-RAID1/home 4 HDD : -> RAID10 soft (md1) -> Luks Partition -> LVM (PV : /dev/mapper/...

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

...nd remote + * buffers must be at least 'count' bytes long + * + * Used by FSL_HV_IOCTL_MEMCPY + * + * The 'local' partition is the partition that calls this ioctl. The + * 'remote' partition is a different partition. The data is copied from + * the 'source' paritition' to the 'target' partition. + * + * The buffer in the remote partition must be guest physically + * contiguous. + * + * This ioctl does not support copying memory between two remote + * partitions or within the same partition, so either 'source' or + * 'target' (but not...

...nd remote + * buffers must be at least 'count' bytes long + * + * Used by FSL_HV_IOCTL_MEMCPY + * + * The 'local' partition is the partition that calls this ioctl. The + * 'remote' partition is a different partition. The data is copied from + * the 'source' paritition' to the 'target' partition. + * + * The buffer in the remote partition must be guest physically + * contiguous. + * + * This ioctl does not support copying memory between two remote + * partitions or within the same partition, so either 'source' or + * 'target' (but not...

...nd remote + * buffers must be at least 'count' bytes long + * + * Used by FSL_HV_IOCTL_MEMCPY + * + * The 'local' partition is the partition that calls this ioctl. The + * 'remote' partition is a different partition. The data is copied from + * the 'source' paritition' to the 'target' partition. + * + * The buffer in the remote partition must be guest physically + * contiguous. + * + * This ioctl does not support copying memory between two remote + * partitions or within the same partition, so either 'source' or + * 'target' (but not...

...nd remote + * buffers must be at least 'count' bytes long + * + * Used by FSL_HV_IOCTL_MEMCPY + * + * The 'local' partition is the partition that calls this ioctl. The + * 'remote' partition is a different partition. The data is copied from + * the 'source' paritition' to the 'target' partition. + * + * The buffer in the remote partition must be guest physically + * contiguous. + * + * This ioctl does not support copying memory between two remote + * partitions or within the same partition, so either 'source' or + * 'target' (but not...