Re: smbfs hang
Chris Coleman wrote: I'm doing a large transfer from an SMB mounted drive, about 2TB of files. After about 250G, it hanging. Of course any process that tries to access that drive hangs as well. Is there anyway to get those processes killed off and remount the drive without rebooting? I haven't had much luck so far. They don't seem to want to die. I'm pretty sure that your answer is going to be no. Most of my experience with SMBFS comes in the opposite direction - trying to write large files to an SMB-mounted filesystem and that was so problematic that we switched to NFS. That's a bit more work to set up, but well worth it, imho. See http://technet.microsoft.com/en-us/library/bb463212.aspx So far, fingers cross and touch wood, with Windows virus checking turned off on the remote drive, writing large files has been problem free and tests reading those files have had no problems either. Only talking in the 40Gb range though. hth, --Alex PS The problems we experienced didn't include wedging, iirc. Files would fail to rename, but if you waited 30 seconds and looked for your target file, it would, hey presto, have appeared. But writes also timed out, taking, in this case, a backup job with it. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
lock test from sh script
Hi all! I need to check if file is locked or not (with flock) from a shell script. I remember there was something but cannot recall what exactly. And if possible I do not want to write my own test utility even it is several lines in length) Thanks, -ip ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lock test from sh script
Igor Pokrovsky [EMAIL PROTECTED] writes: I need to check if file is locked or not (with flock) from a shell script. I remember there was something but cannot recall what exactly. And if possible I do not want to write my own test utility even it is several lines in length) lockf -t0 file true DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lock test from sh script
On Friday 17 October 2008, Igor Pokrovsky wrote: Hi all! I need to check if file is locked or not (with flock) from a shell script. I remember there was something but cannot recall what exactly. And if possible I do not want to write my own test utility even it is several lines in length) Thanks, -ip Perhaps you mean lockf(3) ? -- Pieter de Goeje ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: lock test from sh script
On Friday 17 October 2008 20:18:20 Igor Pokrovsky wrote: I need to check if file is locked or not (with flock) from a shell script. I remember there was something but cannot recall what exactly. And if possible I do not want to write my own test utility even it is several lines in length) lockf -s -t 0 /path/to/file /bin/echo -n if [ $? -eq 75 ]; then echo file is locked exit fi -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: FreeBSD and ISCSI, Strange Problem
Thanks Danny, The patch work fine, but i have new problem: Have two servers 7.0R with iscsi-2.1. They are mounted the same directory way iSCSI. When I create an archive inside of this directory in the server A, the server B don't show the archive, if in the server B to unmount and mount the directory again, the archive created in the server A appears It. Where it is the problem? The storage is Dell MD3000i. Thanks, Daniel Danny Braniss escreveu: the problem is probably that iscsi is deadlocked, so fetch ftp://ftp/users/danny/freebsd/iscsi-2.1.tar.gzs;/ftp/;/.cs.huji.ac.il; ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.1.tar.gz Danny, You typed the ftp wrong. hi Daniel, oh well, it was before coffee :-) Obrigado, thanks !! =) Daniel ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
how determine all possible drivers for my system
Hello maillist of my favorite WortstationServer OS
May i asking: how i can determine all drivers of existing devices, but who is
not present in GENERIC kernel.
For definition of all devices useful to me I have written the following a
little stupid script:
--
#!/bin/sh
MODLIST=`find /boot/kernel -type f -name *.ko -print`
LOGFILE=/var/tmp/kldlog.txt
# ignore for kldload module
IGNORE_MODLIST=/boot/kernel/kernel.ko /boot/kernel/tom.ko
/boot/kernel/iw_cxgb.ko
# (comment: tom.ko and iw_cwbg.ko after loading make kernel panic on my
system)
REPORTS=/var/tmp/reports.txt
FINAL_FILTER=(already exist)|(File exist)|(Unsupported file type)|\
(already present)|(failed to register)|(Exec format error)|\
(symbol [aA-zZ]++ undefin)|(Weak symbols not supported)|\
(already registered)|(unable to register)
# not know another easy way for fopen(/dev/klog)
/etc/rc.d/syslogd stop
echo kern.*${LOGFILE} /var/tmp/syslogd.conf
syslogd -f /var/tmp/syslogd.conf
#
truncate -s0 ${LOGFILE}
for MOD in ${MODLIST}; do
ignore=0
for IGNORE_MOD in $IGNORE_MODLIST; do
if [ ${IGNORE_MOD} = ${MOD} ]; then
ignore=1
fi
done
if [ $ignore -eq 1 ]; then
echo Skipping ${MOD}... ${LOGFILE}
else
echo Try Loading ${MOD}... ${LOGFILE}
sync;
kldload ${MOD} ${LOGFILE} 21
fi
done
/etc/rc.d/syslogd start
egrep -Eiv \${FINAL_FILTER}\ ${LOGFILE} |tee ${REPORTS}
-
Result working off that scripts is the file reports.txt: {
Oct 17 23:51:11 kernel: acpi_aiboost0: ASUStek AIBOOSTER on acpi0
Oct 17 23:51:11 kernel: ppc0: cannot reserve I/O port range
Oct 17 23:51:12 kernel: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24
ascq=0x00 sks=0x48 0x00 0x01
Oct 17 23:51:12 kernel: cd0 at ata3 bus 0 target 0 lun 0
Oct 17 23:51:12 kernel: cd0: PIONEER DVD-RW DVR-212D 1.09 Removable CD-ROM
SCSI-0 device
Oct 17 23:51:12 kernel: cd0: 3.300MB/s transfers
Oct 17 23:51:12 kernel: cd0: Attempt to query device size failed: NOT READY,
Medium not present
Oct 17 23:51:12 kernel: cryptosoft0: software crypto on motherboard
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD dtmalloc.ko: depends on dtrace - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD profile.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD dtraceall.ko: depends on profile - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD profile.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD dtraceall.ko: depends on profile - not available
Oct 17 23:51:13 kernel: KLD dtrace_test.ko: depends on dtraceall - not
available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD profile.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD prototype.ko: depends on dtrace - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD sdt.ko: depends on dtrace
Re: FreeBSD and ISCSI, Strange Problem
In the last episode (Oct 17), Daniel Dias Gonçalves said: Thanks Danny, The patch work fine, but i have new problem: Have two servers 7.0R with iscsi-2.1. They are mounted the same directory way iSCSI. When I create an archive inside of this directory in the server A, the server B don't show the archive, if in the server B to unmount and mount the directory again, the archive created in the server A appears It. Where it is the problem? You can't mount the same UFS filesystem on two servers at once. You'll end up with a horribly-corrupted filesystem, since neither one is aware of changes the other makes. You would need a shared-storage cluster filessytem to be able to do that (or mount the volume read-only on both servers). Mount the filesystem on one server only, then access it via NFS from the other. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how determine all possible drivers for my system
On October 17, 2008 01:21 pm Oleg wrote: Hello maillist of my favorite WortstationServer OS May i asking: how i can determine all drivers of existing devices, but who is not present in GENERIC kernel. snippage My question: what the official FreeBSD-way for the approach similar operations? I tend to use a more trial-and-error method. Basically, it's run pciconf -vl to get a listing of all hardware in the system, and then do searches in man pages, NOTES, and google to find what drivers to test for each device listed as noneX@ (where X is a number). Most of the time, you can guess what the driver will be called based on the type off device listed in pciconf. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Info required] PC Architecture
* Jeroen Ruigrok van der Werven [EMAIL PROTECTED] [081016 08:06] wrote: -On [20081016 16:43], Srinivas ([EMAIL PROTECTED]) wrote: I have a theoretical understanding of the PC architecture and the details but have no idea of how things go under the hood(for a real computer). http://www.amazon.com/dp/0123706068/ - Computer Organization and Design: The Hardware/Software Interface by Patterson and Hennessy http://www.amazon.com/dp/0131485210/ - Structured Computer Organization by Tanenbaum That should answer most, if not all, of your questions on that subject. I also REALLY like: The 8088 Project Book http://www.amazon.com/8088-Project-Book-Robert-Grossblatt/dp/0830631712 Although this isn't a real PC, it will give a nice start in case more technical stuff it too much too soon. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
