similar to: Samba possibly causing windows 2000 to crash?

Dear all, I have samba3.0.23d running on FreeBSD 6.1. It is running with "security = ADS" and has been functioning correctly from about 3.0.14 to 3.0.22. Since I upgraded to 3.0.23(a|b|c|d) group permissions are not honoured by Samba. For example: drwxrwx--- 107 setup domain admins 3072 Nov 15 19:25 install The user setup is a windows admin user; this user can access this

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 All, I'm about to clean and re-initialize a Maxtor 160GB disk that shows a weird problem but I think I've found a bug in RELENG_4_7 somewhere so if preserving my disk can help conquer one more bug I'm happy to wait a couple of days and help solve that bug. Here's the story: While upgrading from 4.3-STABLE to 4.7p4 and at the same time reorganizing my vinum volumes I copied

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

Hello, I am trying to export the results from symnum() while maintain their readability. I tried using sink to text file and also copying and pasting but the results end up looking like this: > symnum(c5.s) bC bED bEN bLP bLS bPA bPD bPR p bbContag 1 bbED + 1 bbENN_MN + B 1 bbLPI , , , 1 bbLSI + B B , 1 bbPAFRAC , * * , * 1 bbPD , B B

After downloading the nightly snapshot last night, I've spent a good part of the day trying to build the package with Borland C++Builder 4. I have some things to report, and also need some help. [Note: this message is long and messy :)] {Converting DSP files to BPR files} I made the necessary BPR files from the DSP files with the Visual C++ Project Conversion Utility. This works okay

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

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

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

CentOS Errata and Bugfix Advisory 2018:1996 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1996 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 52f3ab427f3a47d7541afae2e602e27dd962991ee2f534ed73bf5389dd41cd28 open-vm-tools-10.1.10-3.el7_5.1.x86_64.rpm

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

Hi List, I have a very strange problem with NTBACKUP writing to a SAMBA share. NTBACKUP won't write files bigger than 4.29GB to a SAMBA share. Here are the specs of the systems: SAMBA Server: Slackware 10.1 SAMBA 3.0.21a (large file support turned on) Kernel 2.6.8 / ReiserFS Windows Server: Windows 2003 Server NTBACKUP (latest version) Data to backup is about 50GB

Hi all, I'm experiencing a problem when NTBACKING'UP my W2000 Server files against a Linux 2.4.9 + ReiserFS 3.6 file system + Samba share. It works OK for the first 4 Gb's around file size. Then ntbackup stops serving data and the file on the samba side appears to be downsized to 0 and growing ssssslowly. Once you stop ntbackup by killing the process, the file reappears at its real