search for: ada0p1

...disks-naming.html). For virtio hard drives it is `vtbd'. Under an MBR partition table a slice will be used, so the name of the first partitions will be either `ada0s1a' or `vtbd0s1a'. Under a GPT partition table, where no slice is needed, the name of the first partition will be either `ada0p1' or `vtbd0p1'. Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> --- src/guestfs-internal.h | 2 ++ src/inspect-fs-unix.c | 27 +++++++++++++++++++++++---- src/match.c | 25 +++++++++++++++++++++++++ 3 files changed, 50 insertions(+), 4 deletions(-) diff --git a/src/g...

...irtio hard drives it is `vtbd'. > > Under an MBR partition table a slice will be used, so the name of > the first partitions will be either `ada0s1a' or `vtbd0s1a'. Under a > GPT partition table, where no slice is needed, the name of the first > partition will be either `ada0p1' or `vtbd0p1'. > > Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> I've applied this. I also applied the attached patch, which readds support for the old format, on the assumption that old FreeBSD guests will still exist for some time to come. Hope this is OK. Thanks...

...t is `vtbd'. >> >> Under an MBR partition table a slice will be used, so the name of >> the first partitions will be either `ada0s1a' or `vtbd0s1a'. Under a >> GPT partition table, where no slice is needed, the name of the first >> partition will be either `ada0p1' or `vtbd0p1'. >> >> Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> > > I've applied this. > > I also applied the attached patch, which readds support for the old > format, on the assumption that old FreeBSD guests will still exist for > some time...

Hi, I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire X1470). I installed from a usb memory stick (the default amd64 image), which I booted by pressing "F12" and selecting it from the boot menu on the machine. I installed on a SSD (which replaced the hard drive originally in the machine), using the default scheme for 9.0 (GPT). The installation was painless (many

Hi, I've got a problem with booting zfs-on-root FreeBSD 9.2-PRERELEASE. I'm getting: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool klawisz gptzfsboot: failed to mount default pool klawisz Machine is VM running under KVM on Proxmox 2.3-13. VM has 8 GB of RAM, 400 GB of local storage with SCSI Controller type: Default (lsi). I'm not sure what I did to

...doc/handbook/disks-naming.html). For virtio hard drives it is `vtbd'. Under an mbr partition table a slice will be used, so the name of the first partitions will be either ada0s1a or vtbd0s1a. Under a GPT partition table, where no slice is needed, the name of the first partition will be either ada0p1 or vtbd0p1. Signed-off-by: Nikos Skalkotos <skalkoto at grnet.gr> --- src/guestfs-internal.h | 2 ++ src/inspect-fs-unix.c | 30 +++++++++++++++++++++++++----- src/match.c | 25 +++++++++++++++++++++++++ 3 files changed, 52 insertions(+), 5 deletions(-) diff --git a/src/guestf...

Hi, Is there anything known about ZFS under 10.0-BETA4 when FreeBSD was upgraded from 9.2-RELEASE? I have two servers, with very different hardware (on is with soft raid and the other have not) and after a zpool upgrade, no way to get the server booting. Do I miss something when upgrading? I cannot get the error message for the moment. I reinstalled the raid server under Linux and the other

...swap0 none swap sw 0 0 /dev/gpt/swap1 none swap sw 0 0 /dev/gpt/swap2 none swap sw 0 0 /dev/gpt/swap3 none swap sw 0 0 /dev/gpt/swap4 none swap sw 0 0 root at els1:/usr/src # ll /dev/ada* crw-r----- 1 root operator 0x5f Nov 3 10:01 /dev/ada0 crw-r----- 1 root operator 0x64 Nov 3 10:01 /dev/ada0p1 crw-r----- 1 root operator 0x66 Nov 3 10:01 /dev/ada0p2 crw-r----- 1 root operator 0x74 Nov 3 10:01 /dev/ada0p3 crw-r----- 1 root operator 0x8f Nov 3 10:01 /dev/ada0p3.eli crw-r----- 1 root operator 0x76 Nov 3 10:01 /dev/ada0p4 crw-r----- 1 root operator 0x61 Nov 3 10:01 /dev/ad...

Hello -STABLE@, So I've seen this situation seemingly randomly on a number of both physical 9.1 boxes as well as VMs for I would say 6-9 months at least. I finally have a physical box here that reproduces it consistently that I can reboot easily (ie; not a production/client server). No matter what I do: reboot shutdown -p shutdown -r This specific server will stop at "All buffers