search for: sdd1

...Non-API meta-commands available only in guestfish. diff --git a/tests/btrfs/test-btrfs-devices.sh b/tests/btrfs/test-btrfs-devices.sh index 3935c60..463b0a8 100755 --- a/tests/btrfs/test-btrfs-devices.sh +++ b/tests/btrfs/test-btrfs-devices.sh @@ -66,6 +66,8 @@ btrfs-device-add "/dev/sdc1 /dev/sdd1" / btrfs-device-delete "/dev/sdb1" / btrfs-device-add "/dev/sdb1" / btrfs-device-delete "/dev/sdc1 /dev/sdd1" / +btrfs-replace-start "/dev/sda1" "/dev/sdd1" / force:true +btrfs-replace-start "/dev/sdd1" "/dev/sda1" / forc...

...s/btrfs/test-btrfs-devices.sh b/tests/btrfs/test-btrfs-devices.sh >>>> index 3935c60..463b0a8 100755 >>>> --- a/tests/btrfs/test-btrfs-devices.sh >>>> +++ b/tests/btrfs/test-btrfs-devices.sh >>>> @@ -66,6 +66,8 @@ btrfs-device-add "/dev/sdc1 /dev/sdd1" / >>>> btrfs-device-delete "/dev/sdb1" / >>>> btrfs-device-add "/dev/sdb1" / >>>> btrfs-device-delete "/dev/sdc1 /dev/sdd1" / >>>> +btrfs-replace-start "/dev/sda1" "/dev/sdd1" / force:tr...

...fish. >> diff --git a/tests/btrfs/test-btrfs-devices.sh b/tests/btrfs/test-btrfs-devices.sh >> index 3935c60..463b0a8 100755 >> --- a/tests/btrfs/test-btrfs-devices.sh >> +++ b/tests/btrfs/test-btrfs-devices.sh >> @@ -66,6 +66,8 @@ btrfs-device-add "/dev/sdc1 /dev/sdd1" / >> btrfs-device-delete "/dev/sdb1" / >> btrfs-device-add "/dev/sdb1" / >> btrfs-device-delete "/dev/sdc1 /dev/sdd1" / >> +btrfs-replace-start "/dev/sda1" "/dev/sdd1" / force:true >> +btrfs-replace-start &q...

I've got a usb HD mounted, and it has been mounted since the weekend, and has been kept busy during that period. now I"m done with it an want to umount it, but neither umount nor the on-screen icon (when right-clicked) will let me do it: it is /dev/sdd1, mounted as /media/seagateusb. when root tries to umount it we get this: # umount /media/seagateusb umount: /media/seagateusb: device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) lsof | grep sdd1 gives this: $ lsof | gr...

On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > alex lupu via Syslinux <syslinux at zytor.com> writes: > > ?>? > Obviously it would work IF I moved the vmlinuz > > and initramfs ?files from /dev/sdd2 to /dev/sdd1. > > > > I figured that would probably be considered non-standard Arch > ? ...? > > The standard solution is to have your boot partition (sdd1) mounted as > /boot in your Linux system, and then your kernel and initramfs files are > automatically put (and updated) on the...

...evices.sh b/tests/btrfs/test-btrfs-devices.sh > >>>> index 3935c60..463b0a8 100755 > >>>> --- a/tests/btrfs/test-btrfs-devices.sh > >>>> +++ b/tests/btrfs/test-btrfs-devices.sh > >>>> @@ -66,6 +66,8 @@ btrfs-device-add "/dev/sdc1 /dev/sdd1" / > >>>> btrfs-device-delete "/dev/sdb1" / > >>>> btrfs-device-add "/dev/sdb1" / > >>>> btrfs-device-delete "/dev/sdc1 /dev/sdd1" / > >>>> +btrfs-replace-start "/dev/sda1" "/dev/s...

...ilable only in guestfish. > diff --git a/tests/btrfs/test-btrfs-devices.sh b/tests/btrfs/test-btrfs-devices.sh > index 3935c60..463b0a8 100755 > --- a/tests/btrfs/test-btrfs-devices.sh > +++ b/tests/btrfs/test-btrfs-devices.sh > @@ -66,6 +66,8 @@ btrfs-device-add "/dev/sdc1 /dev/sdd1" / > btrfs-device-delete "/dev/sdb1" / > btrfs-device-add "/dev/sdb1" / > btrfs-device-delete "/dev/sdc1 /dev/sdd1" / > +btrfs-replace-start "/dev/sda1" "/dev/sdd1" / force:true > +btrfs-replace-start "/dev/sdd1" &qu...

...gt; writes: > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> alex lupu via Syslinux <syslinux at zytor.com> writes: >> >>?>? Obviously it would work IF I moved the vmlinuz >>> and initramfs ?files from /dev/sdd2 to /dev/sdd1. >>> >>> I figured that would probably be considered non-standard Arch >> >> The standard solution is to have your boot partition (sdd1) mounted as >> /boot in your Linux system, and then your kernel and initramfs files are >> automatically put (and updated...

...--git a/tests/btrfs/test-btrfs-devices.sh b/tests/btrfs/test-btrfs-devices.sh > >> index 3935c60..463b0a8 100755 > >> --- a/tests/btrfs/test-btrfs-devices.sh > >> +++ b/tests/btrfs/test-btrfs-devices.sh > >> @@ -66,6 +66,8 @@ btrfs-device-add "/dev/sdc1 /dev/sdd1" / > >> btrfs-device-delete "/dev/sdb1" / > >> btrfs-device-add "/dev/sdb1" / > >> btrfs-device-delete "/dev/sdc1 /dev/sdd1" / > >> +btrfs-replace-start "/dev/sda1" "/dev/sdd1" / force:true > >&gt...

I get the following error when trying to mount: Nothing changed (in any case not that I know of). I get the same error from both nodes. Please assist. # mount /u02 mount.ocfs2: Invalid argument while mounting /dev/sdd1 on /u02. Check 'dmesg' for more information on this error. /etc/fstab: /dev/sdd1 /u02 ocfs2 _netdev,datavolume,nointr 0 0 Tail of dmesg: ocfs2_dlm: Nodes in domain ("A7C5B0954A074B36A99739A15F640F2A"): 0 (11528,3):ocfs2_read_locked_inod...

I have my 640GB USB drive connected to a CentOS 5 server and using fdisk, it seems to show a partition of the correct size, /dev/sdd1, but after mounting, the drive shows only 244M size. Does the message received when running fdisk below mean I should reformat this drive, I can't seemed to figure out how to do that with fdisk. Can someone tell me how to reformat, if needed? The drive is empty, I formatted a while back on a De...

...t zytor.com> writes: > On Mon, Mar 16, 2015 at 1:41 PM, Ady via Syslinux <syslinux at zytor.com> > wrote: > >> So, your "root" can still be pointing to sdd2; as long as the >> "vmlinuz-linux" and "initramfs-linux.img" files are located in sdd1 >> directly under the "EFI" directory. > > ?I thought about that. Obviously it would work IF I moved the vmlinuz > and initramfs ?files from /dev/sdd2 to /dev/sdd1. > > I figured that would probably be considered non-standard Arch and > would generate a new set of...

...now at a time that by _randomly_ excluding 'libutil.c32' (among others) from the limited sample that action might jeopardize our beautiful friendship:) Anyway, to eliminate this point of contention once and for all ? (at least for other ? ? readers :), here we go: alex:[~]$ sudo mount /dev/sdd1 /mnt alex:[~]$ ls /mnt EFI alex:[~]$ ls /mnt/EFI syslinux alex:[~]$ ls /mnt/EFI/syslinux cat.c32 cpuid.c32 elf.c32 ifcpu64.c32 lfs.c32 ls.c32 pmload.c32 sanboot.c32 vesainfo.c32 chain.c32 cpuidtest.c32 ethersel.c32 ifcpu.c32 libcom32.c32 lua.c32 power...

...% /bricks/sda1 /dev/sdb1????????????????????????? 7.3T? 557G? 6.8T?? 8% /bricks/sdb1 /dev/sdb1????????????????????????? 7.3T? 557G? 6.8T?? 8% /bricks/sdb1 /dev/sdc1????????????????????????? 7.3T? 630G? 6.7T?? 9% /bricks/sdc1 /dev/sdc1????????????????????????? 7.3T? 630G? 6.7T?? 9% /bricks/sdc1 /dev/sdd1????????????????????????? 7.3T? 683G? 6.7T? 10% /bricks/sdd1 /dev/sdd1????????????????????????? 7.3T? 683G? 6.7T? 10% /bricks/sdd1 /dev/sde1????????????????????????? 7.3T? 657G? 6.7T?? 9% /bricks/sde1 /dev/sde1????????????????????????? 7.3T? 658G? 6.7T?? 9% /bricks/sde1 /dev/sdf1????????????????????...

...: > > > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> alex lupu via Syslinux <syslinux at zytor.com> writes: > >>?>? Obviously it would work IF I moved the vmlinuz > >>> and initramfs ?files from /dev/sdd2 to /dev/sdd1. > >>> I figured that would probably be considered non-standard Arch > >> > >> The standard solution is to have your boot partition (sdd1) mounted as > >> /boot in your Linux system, and then your kernel and initramfs files are > >> automatically put...

...backup). The array cannot be mounted on startup (error message was "missing superblock"). I had to boot from DVD with linux rescue and remove the array from fstab. Here is some info - I am a little dumbfounded. [root at a134-224 log]# cat /proc/mdstat (...) md5 : active raid1 sdb1[0] sdd1[1] 1562505856 blocks [2/2] [UU] ## mdadm examine - I believe the following output indicates that there really *is* a superblock [root at a134-224 log]# mdadm --examine /dev/sdb1 /dev/sdb1: Magic : a92b4efc Version : 0.90.00 UUID : 194e7fdc:2a288e87:c03d8b...

...f LSI disks (Hardware Raid 5) which are attached to a Linux node. The Node has a LSI929 dual fibre channel card that has a channel attached to controller A and B of the array. So we have a list of devices under /proc/partitions mapping what we are expecting to see , for example the devices /dev/sdd1 (A) and /dev/sdx1 (B ) would form a raid 0 device under linux to make a file system slightly under 1TB. This file system was created using the older mkraid utils at the time but has been in production for over a year. This node and the array unfortunately had a power outage and the resulting pr...

...erent site, though that is not the system to which the RAID is currently connected. Just mention that in case this makes a difference, but I presume an fsck would have noticed and fixed anything fundamentally wrong in this regard. David May 15 04:03:30 localhost kernel: Aborting journal on device sdd1. May 15 04:03:30 localhost kernel: EXT3-fs error (device sdd1): ext3_journal_start_sb: Detected aborted journal May 15 04:03:30 localhost kernel: EXT3-fs error (device sdd1): ext3_xattr_get: inode 63343526: bad block 165510584 May 15 04:03:30 localhost kernel: EXT3-fs error (device sdd1) in start_t...

...v to show up /bin/cat: /sys/block/sdd/dev: No such file or directory Device /sys/block/sdd/dev seems to be down. /bin/mknod: missing operand after `b'' Special files require major and minor device numbers. Try `/bin/mknod --help'' for more information. /bin/cat: /sys/block/sdd/sdd1/dev: No such file or directory Waiting 1 seconds for /sys/block/sdd/sdd1/dev to show up /bin/cat: /sys/block/sdd/sdd1/dev: No such file or directory Waiting 2 seconds for /sys/block/sdd/sdd1/dev to show up /bin/cat: /sys/block/sdd/sdd1/dev: No such file or directory Waiting 4 seconds for /sys/...

...icks: Brick1: c107:/exp0 Brick2: c108:/exp0 Brick3: c109:/exp0 Brick4: c110:/exp0 Brick5: c111:/exp0 Brick6: c112:/exp0 Options Reconfigured: cluster.self-heal-window-size: 1024 cluster.data-self-heal-algorithm: full diagnostics.brick-log-level: DEBUG diagnostics.client-log-level: DEBUG c107: /dev/sdd1 ext2 1.8T 1.2T 566G 68% /exp0 c108: /dev/sdd1 ext2 1.8T 1.2T 566G 68% /exp0 c109: /dev/sdd1 ext2 1.8T 1.2T 533G 70% /exp0 c110: /dev/sdd1 ext2 1.8T 1.2T 533G 70% /exp0 c111: /dev/sdd1 ext2 1.8T 1.3T 495G 72% /exp0 c112: /dev/sdd1 ext2 1.8T 1...