similar to: Weird EINVAL readig *large* file

Dear colleagues, experimenting with vinum stripes and mirrors, I'd stuck myself with the following: panic: throw_rude_remark: called without config lock (from vinumconfig.c:throw_rude_remark:103) The system before this panic has two 160G drives with two vinum partitions on each (one for mirrored root and one for the rest with swap between); these were ad0 and ad2. For the experiments,

Dear colleagues, [I'm under 4-STABLE] What is the correct sequence to delete existing vinum module (for example, raid10) and do *not* use -f flags for vinum? in my case t is raid10 vovume: vinum -> l -r t V t State: up Plexes: 2 Size: 8191 MB P t.p0 S State: up Subdisks: 2 Size: 8191 MB P t.p1 S State:

I am trying to setup vinum on a box using 4.8 RELENG_4 (as of about a week ago snapshot). This box was running 4.6 /w vinum on same hard drives for the last 4 months wonderfully... but since it is my current 'scratch/backup' box, I just reinstalled with -STABLE. # uname -a FreeBSD polya.axista.com 4.8-STABLE FreeBSD 4.8-STABLE #22: Tue Jun 24 17:01:07 EDT 2003

I made an array out of 3 IBM 20 gigs and 3 Maxtor 20 gigs I used striping to make one big drive A couple of days ago I was copying a movie onto to it and the computer decided to reboot when it came back up I was greeted with this message Can someone please tell me if I can recover some how? or should I just rebuild the array? or is one of my disks physically bad? Detects all 7 drives (1 10gig

Well, colleagues, I'm stuck a bit. I tried many different ways to setup system with vinum root (the only reference I found yet besides old "bootstrapping vinum" article is Joerg's commit message: http://freebsd.rambler.ru/bsdmail/cvs-all_2003/msg01225.html I failed. I have 4-stable system set up at ad0, and tried to set up pair of drives for new system at ad2 and ad3 (actually,

Hi, I'm not sure this is supposed to happen (my computer rebooted halfway through adding an other drive to a volume): [long lines needed] (02:44:50 <~>) 0 $ sudo vinum ld D storage State: up Device /dev/ad0d Avail: 38166/381 66 MB (100%) D worthless State: up Device /dev/ad2d Avail: 38038/380 38 MB (100%) D barracuda

Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic

I've just had a 4.9p1 system partially deadlock for about 30 minutes and then spontaneously(?) recover. The "ps" results point at vinum. I've never seen this before and don't recall anything like this being mentioned here before. At the time, I had two find's running in a large NFS mounted filesystem and was doing a "cvs -d /usr/ncvs -R checkout -P ports" from

Hi all, I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to manage big number of file systems but PAE enabled kernel does not compile modules. I couldn't figure out how to get vinum statically compiled in the kernel if that is the way to go. I am running 6-STABLE. Please advise on how to get PAE kernel and gvinum working together! TIA, Stoyan

It might sound stupid, but I'd like to know if there's any difference. Are those 3 line the same? WITH_KMS=YES WITH_KMS="YES" WITH_KMS=yes Best regards Zoran

FreeBSD 4.1.1-RELEASE #1: Tue Oct 10 18:09:51 CDT 2000 root@test-drive.tamu.edu:/usr/src/sys/compile/TEST-DRIVE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM

I am using the following: Samba 2.2.8a (from FreeBSD ports) FreeBSD 4.7-RELEASE-p10 Samba is configured as a member of a Windows 2000 domain. Generally everything seems to be working as expected. Occasionally the following gets logged to the console: [2003/04/14 20:25:19, 0] smbd/service.c:make_connection(599) zulu (192.168.1.161) Can't change directory to /data/path (No such file or

Howdy all. We're experiencing some difficulties encountered from a new build/install world/kernel on a Compaq Proliant machine we have. We were running fine under 4.7-STABLE, and updated the sources to 4.8-STABLE last night (5/8/03), built and installed. This morning after a reboot, we got a horrid error to the likes of: Error mounting root. Error no 22. We encountered this error earlier

Hello everyone, I have a 50-client Samba installation here (version of Samba is 3.0.12). The problem is, that files are not locked correctly. The scenario is the following: 1. User A opens a word document file and edits it 2. User B tries to open the same file, too 3. Instead of getting a warning that the file is in use by another user (like it was when we had NT4), Word opens the file without

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

Package: blktap-utils Version: 2.0.90-2 Severity: important Tapdisk fails to start and exit's silently after failing to detect current kernel version. This happens only on newer kernel versions missing sublevel field. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP

On Thu, Dec 13, 2018 at 05:53:50PM +0300, Pavel Tikhomirov wrote: > We've failed to copy and process vhost_iotlb_msg so let userspace at > least know about it. For instance before these patch the code below runs > without any error: > > int main() > { > struct vhost_msg msg; > struct iovec iov; > int fd; > > fd = open("/dev/vhost-net",

From: Pavel Tikhomirov <ptikhomirov at virtuozzo.com> Date: Thu, 13 Dec 2018 17:53:50 +0300 > We've failed to copy and process vhost_iotlb_msg so let userspace at > least know about it. For instance before these patch the code below runs > without any error: ... > Signed-off-by: Pavel Tikhomirov <ptikhomirov at virtuozzo.com> Michael, will you be taking this in via

When guestfs_lvm_canonical_lv_name was called with a /dev/dm* or /dev/mapper* name which was not an LV then a noisy error would be printed. This would typically have happened with encrypted disks, and now happens very noticably when inspecting Windows BitLocker- encrypted guests. Using the modified error behaviour of this API from the previous commit we can now hide that error in that specific

This is the patch I tested which works (on top of the patch posted): diff --git a/lib/canonical-name.c b/lib/canonical-name.c index e0c7918b4..ae4def692 100644 --- a/lib/canonical-name.c +++ b/lib/canonical-name.c @@ -53,8 +53,16 @@ guestfs_impl_canonical_device_name (guestfs_h *g, const char *device) * BitLocker-encrypted volume, so simply return the original * name in that case.