similar to: Exporting which partitions to md-configure

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

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

If you export two subvolumes of a btrfs filesystem, they will both be given the same uuid so lookups will be confused. blkid cannot differentiate the two, so we must use the fsid from statfs64 to identify the filesystem. We cannot tell if blkid or statfs is best without knowing internal details of the filesystem in question, so we need to encode specific knowledge of btrfs in mountd. This is

NFS needs a unique identifier for a filesystem to be able to export it. This can be set by the admin (fsid= in /etc/exports) but that is a hassle and it is best to set it automatically. nfs-utils currently uses the UUID returned by libblkid if that works, or the fsid returned by statfs64 if libblkid finds nothings and fsid is non-zero. Otherwise it uses device major/minor. This

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've read through the archives and it looks like people are using ext3 with software RAID with at least some success. I just want to confirm that it works properly. If I convert my md RAID 0 to ext3, should I expect A) A fast journalled filesystem, or B) Wailing and gnashing of teeth My RAID currently does not use persistant superblocks, because I created it many moons ago under the old

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

On 06/27/2011 07:46 AM, NeilBrown wrote: > On Thu, 23 Jun 2011 12:53:37 +0200 Nico Schottelius > <nico-lkml-20110623@schottelius.org> wrote: > >> Good morning devs, >> >> I''m wondering whether the raid- and volume-management-builtin of btrfs is >> actually a sane idea or not. >> Currently we do have md/device-mapper support for raid >>

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

From: Pino Toscano <ptoscano@redhat.com> --- daemon/devsparts.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/daemon/devsparts.c b/daemon/devsparts.c index b764f63..852ee99 100644 --- a/daemon/devsparts.c +++ b/daemon/devsparts.c @@ -20,6 +20,7 @@ #include <stdio.h> #include <stdlib.h> +#include <stdbool.h> #include

I'm running Linux travis 2.6.15-1-686 #2 Mon Mar 6 15:27:08 UTC 2006 i686 GNU/Linux on a laptop with ext3 on / Some time ago things started getting weird in the following way: I do a fairly normal hack, ^Z, make, test loop when developing and it seems that vim is calling fsync or sync and that is then flushing everything to disk. My tests create maybe 10 dozen files in ~30MB and for some

Sorry this is off-topic, but I'm scrambling to get this system in, google didn't help, and I'm sure someone on this list knows the answer cold. I'm trying to nfs-export a tmpfs disk. I saw a hint from a response about ram disks... which leads to my guess that tmpfs simply doesn't implement some method that nfsd needs. I can probably survive without tmpfs, but I'd like 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:

I don't see any mention of this in the archives and maybe it's a stupid question but... I have a separate partition for /var and it is an ext3 partiition. When I try to reboot, /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

Hello, in regard to https://bugzilla.redhat.com/show_bug.cgi?id=1434066 i have been faced to another issue when using the trashcan feature on a dist. repl. volume running a geo-replication. (gfs 3.12.6 on ubuntu 16.04.4) for e.g. removing an entire directory with subfolders : tron at gl-node1:/myvol-1/test1/b1$ rm -rf * afterwards listing files in the trashcan : tron at gl-node1:/myvol-1/test1$

Hi, I am trying out ext3 with an external journal (on a battery backed RAM card). I use data=journal, and sync nfs writes go nice and fast :-) But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it

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

I'm running Red Hat Linux 5.0/Intel with samba-1.9.18p7-50.1. The PC I have has a hard disk with a /dev/hda1 which is a Win 95 partition and a /dev/hda3 which is a Linux partition. The mount looks like this: /dev/hda3 on / type ext2 (rw) /dev/hda1 on /win95 type vfat (rw,gid=100,umask=0002) and the gid=100 is the group users and contains only myself, chj. The mount point /win95 is owned by

Hi, Fist of all thanks for all the work you put into gluster this product is fantastic. In our setup, we have to have some kind of nfs authentication. Not beeing able to set the rpc-auth option using the cli was a big draw-back for us. Setting the option auth.allow only set the gluster auth.addr.allow option in the bricks themselves but did not do any good regarding nfs access. Setting the