Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: Well having run many very large scale projects myself I find it difficult to accept either implication of this perspective. There's a massive difference between running a large commercial project and running a large open source project using volunteers. On a commercial project, you can direct someone to do something and they have a choice of either doing it or finding another job. On a volunteer project, there's a limit to how far you can push someone to do something they don't enjoy before they just leave. The first implication is that we should be complacent about it and not seek to find a method to improve the process. I don't think anyone is suggesting this. In my experience, the FreeBSD project is always open to process improvements - this is especially obvious in the documentation and release engineering areas. Most of our really top notch developers are actually very bad at documenting their work (I don't mean bad at being timely with it, I mean that they are bad at DOING it), and frankly their time is better spent elsewhere. That is a judgment call - franky my experience has been that developers who are bad at ensuring their work is well documentated are second rate rather than top rate developers. Software developers are notoriously poor at writing documentation for non-technical people. There are probably very few developers who enjoy writing end-user documentation (and can write). In my experience, especially on large projects, it's rare for developers to write the end-user documentation. They may write a rough outline but it's the technical writers who actually do the documentation. The problem is finding people with technical writing skills who are interested in helping with FreeBSD. It's also worth noting that a number of FreeBSD developers are not native English speakers. It's probably unreasonable to expect them to write polished English documentation. What I have found works in development is to create team relationships that cover design, development and documentation. I agree that this is a good approach. It's similar to the 'surgical team' approach that Brooks recommends in The Mythical Man-Month. I think that this does happen to some extent in FreeBSD but agree it could be more widespread. (Though it is probably harder to put it into practice in a distributed, volunteer project than when the team share a cubicle). My view would be that the freebsd project might do well to consider implementing a no release without quality documentation assurance policy. ... development is so good. It deserves better and more professional attention to the role of end user documentation. Are you volunteering? -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
pw groupdel misbehavior?
Yo list!
I just encountered something I think w/c is not right, e.g.:
[EMAIL PROTECTED]:~# cat /etc/group
# $FreeBSD: src/etc/group,v 1.31 2004/06/23 01:32:28 mlaier Exp $
#
wheel:*:0:root,mars
daemon:*:1:
kmem:*:2:
sys:*:3:
tty:*:4:
operator:*:5:root
mail:*:6:
bin:*:7:
news:*:8:
man:*:9:
games:*:13:
staff:*:20:
sshd:*:22:
smmsp:*:25:
mailnull:*:26:
guest:*:31:
bind:*:53:
proxy:*:62:
authpf:*:63:
_pflogd:*:64:
uucp:*:66:
dialer:*:68:
network:*:69:
www:*:80:
nogroup:*:65533:
nobody:*:65534:
pgsql:*:70:
[EMAIL PROTECTED]:~# pw groupdel -g bleh
[EMAIL PROTECTED]:~# cat /etc/group
# $FreeBSD: src/etc/group,v 1.31 2004/06/23 01:32:28 mlaier Exp $
#
daemon:*:1:
kmem:*:2:
sys:*:3:
tty:*:4:
operator:*:5:root
mail:*:6:
bin:*:7:
news:*:8:
man:*:9:
games:*:13:
staff:*:20:
sshd:*:22:
smmsp:*:25:
mailnull:*:26:
guest:*:31:
bind:*:53:
proxy:*:62:
authpf:*:63:
_pflogd:*:64:
uucp:*:66:
dialer:*:68:
network:*:69:
www:*:80:
nogroup:*:65533:
nobody:*:65534:
pgsql:*:70:
The previous action of deleting an invalid group (bleh) passed on to
-g via pw results in the 'wheel' group being deleted outright,
silently. Ouch.
As an avid user of 'pw' I keep on inter-changing the -n and -g
switches (when working w/ pw user{add/mod/del} and pw
group{add/mod/del}), so it struck me when i realized I issued the
command above and the jail didnt know the 'wheel' group anymore when i
went on to do some other stuff (was installing ports when it didn't
know who's 'wheel', heh ;-)
This happens on 5.4R and 6.0R, on my boxens.
Thanks and FYI!
cheers
mars
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
mcast-tools make my 6.0-STABLE kernel panic
Dear All, my router box uname -a FreeBSD ipv6.ppk.itb.ac.id 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Dec 7 20:53:11 WIT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PPK i386 installed zebra-0.95 from ports/net (zebra, ospfd, and ospf6d works well) and then I installed mcast-tools from ports/net when I try to run pim6sd I got kernel panic. panic: register_mif0: BUG: if_attach called without if_alloc'd input() KDB: stack backtrace: kdb_backtrace(100,c4091600,c0721ff4,d7437c20,c0721be0) at 0xc0519645 = kdb_backtrace+0x29 panic(c06b1a72,c0721bf0,d7437b84,d7437b8c,c056652d) at 0xc0501db8 = panic+0xa8 if_attach(c0721be0,c0721be0,c06b851c,0) at 0xc0563a23 = if_attach+0x33 add_m6if(d7437c20) at 0xc05b2909 = add_m6if+0xa9 ip6_mrouter_set(c35e3000,d7437c90) at 0xc05b2381 = ip6_mrouter_set+0x91 rip6_ctloutput(c35e3000,d7437c90,c5cf312c,0,c06aeabd) at 0xc05c0503 = rip6_ctloutput+0xa3 sosetopt(c35e3000,d7437c90,c3e75e58,1,29) at 0xc0539ab8 = sosetopt+0x2c kern_setsockopt(c4091600,d7437d04,5,1,296) at 0xc053e27a = kern_setsockopt+0xb5 setsockopt(c4091600,d7437d04,5,1,296) at 0xc06721af = setsockopt+0x1e syscall(3b,3b,bfbf003b),1,8073588) at 0xc06271af = syscall+0x22f Xint0x80_syscall() at 0xc0661bbf = Xint0x80_syscall+0x1f --- syscall (105, FreeBSD ELF32, setsockopt), eip = 0x2810cd5f, esp = 0xbfbfea0c, ebp = 0xbfbfea48 --- KDB: enter: panic [thread pid 14460 tid 100185] Stopped at 0xc05196c7 = kdb_enter+0x2b: nop db bt Tracing pid 14460 tid 100185 td 0xc4091600 kdb_enter(c06a989e) at 0xc05196c7 = kdb_enter+0x2b panic(c06b1a72,c0721bf0,d7437b84,d7437b8c,c056652d) at 0xc0501db8 = panic+0xbb if_attach(c0721be0,c0721be0,c06b851c,0) at 0xc0563a23 = if_attach+0x33 add_m6if(d7437c20) at 0xc05b2909 = add_m6if+0xa9 ip6_mrouter_set(c35e3000,d7437c90) at 0xc05b2381 = ip6_mrouter_set+0x91 rip6_ctloutput(c35e3000,d7437c90,c5cf312c,0,c06aeabd) at 0xc05c0503 = rip6_ctloutput+0xa3 sosetopt(c35e3000,d7437c90,c3e75e58,1,29) at 0xc0539ab8 = sosetopt+0x2c kern_setsockopt(c4091600,d7437d04,5,1,296) at 0xc053e27a = kern_setsockopt+0xb5 setsockopt(c4091600,d7437d04,5,1,296) at 0xc06721af = setsockopt+0x1e syscall(3b,3b,bfbf003b),1,8073588) at 0xc06271af = syscall+0x22f Xint0x80_syscall() at 0xc0661bbf = Xint0x80_syscall+0x1f with best regards, -dikshie- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 as storage server with raid5?
Torfinn Ingolfsen wrote: I was thinking about gvinum for the storage server, but given the current documentation and the discussions about it now, I don't want to risk it. So, I'm looking at hardware raid 5 controllers. From this list, You could use graid3(8) - it has data+parity components like raid5. I've been using it for more than a year now and didn't have problems with it. Didn't have to try recovery from a dead disk also, but should work ok. It's like regular RAID3 but uses sector-sized data chunks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, Dec 08, 2005 at 12:18:57AM +0100, Torfinn Ingolfsen wrote: I was thinking about gvinum for the storage server, but given the current documentation and the discussions about it now, I don't want to risk it. IMHO it's pretty stable in 6.0. I've been running gvinum RAID-5 for a while now; other than one strange panic (something to do with out of memory situations, see kern/89660) I haven't had a hitch yet. That said, I haven't needed to replace a disk yet either (I've demoed this but it was not yet needed in production use). In short, don't write gvinum off just yet. Documentation is around the corner (as a result of a SoC project). --Stijn -- Well, Brahma said, even after ten thousand explanations, a fool is no wiser, but an intelligent man requires only two thousand five hundred. -- The Mahabharata. pgpW4eaFpgDLj.pgp Description: PGP signature
Re: Copying kernel and OS
It should work fine. You need to preserve mod and access times as well as flags and permissions. If you are going to do this on a repeated basis, I'd look into something like cvsup or rsync, maybe even mirror, to keep the slow machines directory structures in sync rather than a cp -Rp. Paul. Jack Raats wrote: *** This message has been scanned by the InterScan for CSC-SSM and found to be free of known security risks. *** Is it also possible to scp both directories to the slow machine? JAck - Original Message - From: Stephen Montgomery-Smith [EMAIL PROTECTED] To: Jack Raats [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org; FreeBSD Stable freebsd-stable@freebsd.org Sent: Wednesday, December 07, 2005 10:29 PM Subject: Re: Copying kernel and OS Jack Raats wrote: I've two machines running FreeBSD 6.0-STABLE. One very fast machine and one very very slow machine. On the fast machine I can compile a new kernel and OS very quickly and easily. Is it possible to transfer the compile world and kernel to the slow machine. If yes whart directories etc... do i have to transfer. Jack I do something like this. I build on the fast machine, and then use NFS to allow the slow machine to access /usr/src and /usr/obj. I have found that it is important to preserve the names of the directories, so that they are also called /usr/src and /usr/obj on the slow machine. Then I just do mergemaster, make installworld, make installkernel (in the appropriate order) on the slow machine, and it works like a charm. The entries in fstab are like this: hub2:/usr/obj/usr/objnfs rw,bg,noauto0 0 hub2:/usr/src/usr/srcnfs rw,bg,noauto0 0 where hub2 is the name of the fast machine. In /etc/exports on hub2 I have something like this /usr -maproot=root -alldirs -network 10.0.0.0 -mask 255.255.255.0 (here 10.0.0.0 is the IP addresses of my LAN) and in /etc/rc.conf on hub2 I have some lines like nfs_server_enable=YES rpcbind_enable=YES Then on the slow machine I simply type mount /usr/src mount /usr/obj -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- __ Paul T. Root /_ \ 1977 MGB / /|| \\ ||\/ || _ | || || || \ ||__// \__/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
some more on Re: Adventurous fix for wheel mouse not working in FreeBSD 6.0
On Wednesday 07 December 2005 19:22, Torfinn Ingolfsen wrote: And scrolling does NOT work. I found out this for releng_6 and appearently is the same on former versions since all call the same problem: when you set in xorg.conf any other option as Option Protocol auto the scroll buttons are not working, doesn't matter which and how many buttons you configure and which of them you set in [Z|X]Axismapping I need to say I have a NB with synaptics touchpad. basicly setting Driver mouse Identifier touchpad Option Device /dev/psm0 Option Protocol PS/2 or Option Protocol auto and the touchpad works as mouse, tapping, clicking tap+drag and double click as well as left and right button fuctions but no scroll using xev the 4,5,6 and 7 button are not even recognized so I guess the problem is on the PS/2 driver and not in Xorg and it does not matter if I set Option Buttons 7 Option ZAxisMapping 4 5 Option XAxisMapping 6 7 then, when I set in loader.conf hw.psm.synaptics_support=1 the synaptics touchpad is probed and I can see it in dmesg but it still does not work as PS/2 protocol Soon I set Option Protocol auto I get the 7 buttons and I can scroll up and down and left and right BUT I can not tap+drag anymore, to drag I need to press the phisical left button and the I can drag using the touchpad Also it doesn't matter if I use moused and sysmouse in xorg.conf,only using the synaptic with sysmouse is very nervous and almost unusable, the pointer runs around by itself almost even if configuring, the aditional buttons are dead, xev doesn't find them I guess PS/2 does not know more than 2 buttons and could perhaps emulate the third probable PS/2 protocol/driver should be revised to get the additional buttons found. João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Copying kernel and OS
On 2005-12-08 07:02, Jack Raats [EMAIL PROTECTED] wrote: Is it also possible to scp both directories to the slow machine? Maybe, but why do that? NFS is going to work better :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Fatal trap 12: page fault while in kernel mode
Hello.
While copying a few directories from one machine to my new notebook (tar
over ssh over wireless connection [if_iwi]), the notebook paniced with
the following:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x52535307
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc078bc08
stack pointer = 0x28:0xde4ae95c
frame pointer = 0x28:0xde4ae984
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 761 (bsdtar)
trap number = 12
panic: page fault
Uptime: 11m20s
Dumping 502 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 502MB (128464 pages) 486 470 454 438 422 406 390 374 358 342
326 310 294 278 262 246 230 214 198 182 166 150 134 118 102 86 70 54 38
22 6
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc0638202 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:399
#2 0xc0638498 in panic (fmt=0xc084e5a2 %s)
at /usr/src/sys/kern/kern_shutdown.c:555
#3 0xc0807c30 in trap_fatal (frame=0xde4ae91c, eva=1381192455)
at /usr/src/sys/i386/i386/trap.c:831
#4 0xc080799b in trap_pfault (frame=0xde4ae91c, usermode=0,
eva=1381192455)
at /usr/src/sys/i386/i386/trap.c:742
#5 0xc08075d9 in trap (frame=
{tf_fs = 8, tf_es = -565575640, tf_ds = -1065943000, tf_edi =
-565515340, tf_esi = -1043806720, tf_ebp = -565515900, tf_isp =
-565515960, tf_ebx = -1039299392, tf_edx = 170, tf_ecx = 1, tf_eax =
1381191775, tf_trapno = 12, tf_err = 0, tf_eip = -1065829368, tf_cs =
32, tf_eflags = 66051, tf_esp = -1064527936, tf_ss = -565515812}) at
/usr/src/sys/i386/i386/trap.c:432
#6 0xc07f6dca in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc078bc08 in ufsdirhash_lookup (ip=0xc20ec318,
name=0xc1c45810 UPCII.TTF, namelen=9, offp=0x5253505f,
bpp=0x5253505f,
prevoffp=0x0) at /usr/src/sys/ufs/ufs/ufs_dirhash.c:409
#8 0xc078d480 in ufs_lookup (ap=0xde4aea80)
at /usr/src/sys/ufs/ufs/ufs_lookup.c:209
#9 0xc0816d64 in VOP_CACHEDLOOKUP_APV (vop=0x5253505f, a=0xaa)
at vnode_if.c:150
#10 0xc0682c9e in vfs_cache_lookup (ap=0x5253505f) at vnode_if.h:82
#11 0xc0816cf3 in VOP_LOOKUP_APV (vop=0xc08fbf40, a=0xde4aeb18)
at vnode_if.c:99
#12 0xc068722d in lookup (ndp=0xde4aeba0) at vnode_if.h:56
#13 0xc0686b6e in namei (ndp=0xde4aeba0) at
/usr/src/sys/kern/vfs_lookup.c:203
#14 0xc0694367 in kern_lstat (td=0xc1fea900,
path=0xaa Address 0xaa out of bounds, pathseg=170, sbp=0xde4aec74)
at /usr/src/sys/kern/vfs_syscalls.c:2102
#15 0xc0694303 in lstat (td=0xc1fea900, uap=0xde4aed04)
at /usr/src/sys/kern/vfs_syscalls.c:2086
#16 0xc0807f47 in syscall (frame=
{tf_fs = 59, tf_es = 4259899, tf_ds = -1078001605, tf_edi =
-1077941792, tf_esi = -1077941248, tf_ebp = -1077941560, tf_isp =
-565514908, tf_ebx = 134672409, tf_edx = 134586905, tf_ecx = 25, tf_eax
= 190, tf_trapno = 0, tf_err = 2, tf_eip = 672111379, tf_cs = 51,
tf_eflags = 658, tf_esp = -1077941860, tf_ss = 59}) at
/usr/src/sys/i386/i386/trap.c:976
#17 0xc07f6e1f in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:200
#18 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb)
The notebook runs GENERIC kernel of 6.0-RELEASE.
I don't know if it's known issue or not, nor it is reproducible. If
dmesg would be helpful, I can post it as well. I will keep the vmcore.0
for a while, too, just in case.
--
Krzysztof Kowalik | () ASCII Ribbon Campaign
Computer Center, AGH UST| /\ Support plain text e-mail
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
On Thu, Dec 08, 2005 at 08:34:42PM +1100 I heard the voice of Peter Jeremy, and lo! it spake thus: On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: development is so good. It deserves better and more professional attention to the role of end user documentation. Are you volunteering? It should be noted that this sort of response often comes across rather sneering and snarky, but (most of the time, anyway) it's really not meant to. It often DOES translate pretty directly to Yes, that would be nice, and it would be really great if somebody who was interested and capable were to grab the reins and do it. -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: permanent per month panic on 5.4-p4
On Thu, Dec 08, 2005 at 09:50:50AM +0200 I heard the voice of Oleg Palij, and lo! it spake thus: Unfortunately this trace looks corrupted. Are you building your kernel with -O2? I guess that no. Isn't -O2 the default now if you're not explicitly setting it otherwise? -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
From: Peter Jeremy [EMAIL PROTECTED] Date: 2005/12/08 Thu AM 01:34:42 PST To: Vizion [EMAIL PROTECTED] CC: Doug Barton [EMAIL PROTECTED], freebsd-stable@freebsd.org Subject: Re: Upgrading 5.3 6.0 buildworld failure now in libmagic On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: Well having run many very large scale projects myself I find it difficult to accept either implication of this perspective. There's a massive difference between running a large commercial project and running a large open source project using volunteers. Not really I have done both and found that shared values and community collaboration work the same. On a commercial project, you can direct someone to do something and they have a choice of either doing it or finding another job. Well that kind of development environment (rule by dictat) does not work very well. Developers are people who are engaged in a collaborative process. If you encourage them to think like prima donas then they will behave like prima donas rather than as part of an integrated team. On a volunteer project, there's a limit to how far you can push someone to do something they don't enjoy before they just leave. Push has it limitations everywhere.. goals and communal rewards are better in both volunteer and commercial projects. The first implication is that we should be complacent about it and not seek to find a method to improve the process. I don't think anyone is suggesting this. In my experience, the FreeBSD project is always open to process improvements - this is especially obvious in the documentation and release engineering areas. The question is about the degree of committment to process change not whwther it is absent or present. The critique is there is tooo little comitment to process change and too much resistance to greater concentration on the quality of user docuimentation and the significance of that work in the developmenmt cycle. Most of our really top notch developers are actually very bad at documenting their work (I don't mean bad at being timely with it, I mean that they are bad at DOING it), and frankly their time is better spent elsewhere. That is a judgment call - franky my experience has been that developers who are bad at ensuring their work is well documentated are second rate rather than top rate developers. Software developers are notoriously poor at writing documentation for non-technical people. There are probably very few developers who enjoy writing end-user documentation (and can write). In my experience, especially on large projects, it's rare for developers to write the end-user documentation. NOTE I said F:ranky my experience has been that developers who are bad at ENSURING their work is well documentated are second rate rather than top rate developers. The work of the technical writer needs to influence development at the design stage! It does not matter whether the developer does or does not write the the documentation but it does matter whether the developer is COMIITED to both ensuring that there is proper documentation AND that the documentation process is an integral part of the development process that influences its outcome. They may write a rough outline but it's the technical writers who actually do the documentation. The outline for user documentation needs to be structured BEFORE development begins NOT as an afterthought. In a well structured development environment documentation is part of DESIGN not post design implementation . That is because thinking about end user at the design stage is necessary if the outcome of the process is going to be user centric. The problem is finding people with technical writing skills who are interested in helping with FreeBSD. Freebsd needs to reorganize the way it develops if it is going to interest techn ical writers. No technical writer wants to be associated with writing documnets for developments that have been poorly designed for the end user. Clearing up someone else's mess is no fun. If you treat technical writers as people who come along afterwards and pick up yopur trash OF COURSE you will not get them involved. You need to ask WHY it is difficult to get them. It is because freebsd does not produce software with a focus on end user satisfaction. This is a chicken and egg problem that can only be solved by a fu8ndamental shift both the focus of development objectives and the development process. It's also worth noting that a number of FreeBSD developers are not native English speakers. It's probably unreasonable to expect them to write polished English documentation. What I have found works in development is to create team relationships that cover design, development and documentation. I agree that this is a good approach. It's similar to the 'surgical team' approach that Brooks recommends in The Mythical Man-Month. I think that
Re: Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
From: Matthew D. Fuller [EMAIL PROTECTED] Date: 2005/12/08 Thu AM 08:01:47 PST To: Peter Jeremy [EMAIL PROTECTED] CC: Doug Barton [EMAIL PROTECTED], freebsd-stable@freebsd.org, Vizion [EMAIL PROTECTED] Subject: Re: Upgrading 5.3 6.0 buildworld failure now in libmagic On Thu, Dec 08, 2005 at 08:34:42PM +1100 I heard the voice of Peter Jeremy, and lo! it spake thus: On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: development is so good. It deserves better and more professional attention to the role of end user documentation. Are you volunteering? It should be noted that this sort of response often comes across rather sneering and snarky, but (most of the time, anyway) it's really not meant to. It often DOES translate pretty directly to Yes, that would be nice, and it would be really great if somebody who was interested and capable were to grab the reins and do it. Do you mean the response sounds like freebsd documentation chuckles See my last email for a response to that one ! ATM I am struggling on a win machine because my local server once more refused to upgrade to 6.0 and this time has bombed outcompletely - looks nlike a complete rebuild david -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
bsdtar / libarchive bug?
It seems bsdtar can create files it cant read. i.e. it will happily create
empty tar.gz files but when it comes to read them the following error
is output:
tar: Unrecognized archive format: Inappropriate file type or format
Having a look at libarchive shows the following code:
/* An empty archive is a serious error. */
if (bytes_read == 0) {
archive_set_error(a, ARCHIVE_ERRNO_FILE_FORMAT,
Empty input file);
return (ARCHIVE_FATAL);
}
Which is where I expect the issue is, why would an empty archive
be fatal? I can see any reason for this, yes its strange but there's
nothing fatal about it imo.
Steve
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone (023) 8024 3137
or return the E.mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
Peter Jeremy wrote: On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: That is a judgment call - franky my experience has been that developers who are bad at ensuring their work is well documentated are second rate rather than top rate developers. Software developers are notoriously poor at writing documentation for non-technical people. There are probably very few developers who enjoy writing end-user documentation (and can write). My personal expectation is *not* that the FreeBSD developers tell me what a cdrom is. My expectation is that they tell me what works, what doesn't, and warn me about whats in the middle. Trust me, there are damn few non-technical people installing FreeBSD, and I'm pretty sure both of them gave up in sysinstall. I can read (most) code and I can search PR's. However, if it's 2 am and my server has puked on it's shoes during an upgrade due to an undocumented issue the developer knew about, I'm not going to recommend FreeBSD to anyone other than as a hobby for single men with beards. In my experience, especially on large projects, it's rare for developers to write the end-user documentation. They may write a rough outline but it's the technical writers who actually do the documentation. The problem is finding people with technical writing skills who are interested in helping with FreeBSD. It's also worth noting that a number of FreeBSD developers are not native English speakers. It's probably unreasonable to expect them to write polished English documentation. Again, I'm not asking them to write chapters in the handbook and I understand (and assumed) they may not be native English speakers. How hard is it to get a, ata.c broke with via 666 sata chipset under heavy load? If I have a via 666 sata chipset, now I know to go looking in the code. Even if don't go looking in the code, I know that I might want to look at a different adapter. Don't tell me whats little more than a subject line of a mail message is beyond even a junior non-English speaking coder and a few minutes with a translation program. Are you volunteering? Yes, I'd like to help, not that I think my writing skills are all that great. But no if the developers won't be forthcoming with details. P.S. I'm not picking on the ata code or it's owners. It was just a module name I knew off hand. jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
On Thursday 08 December 2005 08:57, [EMAIL PROTECTED] wrote: From: Peter Jeremy [EMAIL PROTECTED] Date: 2005/12/08 Thu AM 01:34:42 PST To: Vizion [EMAIL PROTECTED] CC: Doug Barton [EMAIL PROTECTED], freebsd-stable@freebsd.org Subject: Re: Upgrading 5.3 6.0 buildworld failure now in libmagic On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: Well having run many very large scale projects myself I find it difficult to accept either implication of this perspective. There's a massive difference between running a large commercial project and running a large open source project using volunteers. Not really I have done both and found that shared values and community collaboration work the same. On a commercial project, you can direct someone to do something and they have a choice of either doing it or finding another job. Well that kind of development environment (rule by dictat) does not work very well. Developers are people who are engaged in a collaborative process. If you encourage them to think like prima donas then they will behave like prima donas rather than as part of an integrated team. On a volunteer project, there's a limit to how far you can push someone to do something they don't enjoy before they just leave. Push has it limitations everywhere.. goals and communal rewards are better in both volunteer and commercial projects. The first implication is that we should be complacent about it and not seek to find a method to improve the process. I don't think anyone is suggesting this. In my experience, the FreeBSD project is always open to process improvements - this is especially obvious in the documentation and release engineering areas. The question is about the degree of committment to process change not whwther it is absent or present. The critique is there is tooo little comitment to process change and too much resistance to greater concentration on the quality of user docuimentation and the significance of that work in the developmenmt cycle. Most of our really top notch developers are actually very bad at documenting their work (I don't mean bad at being timely with it, I mean that they are bad at DOING it), and frankly their time is better spent elsewhere. That is a judgment call - franky my experience has been that developers who are bad at ensuring their work is well documentated are second rate rather than top rate developers. Software developers are notoriously poor at writing documentation for non-technical people. There are probably very few developers who enjoy writing end-user documentation (and can write). In my experience, especially on large projects, it's rare for developers to write the end-user documentation. NOTE I said F:ranky my experience has been that developers who are bad at ENSURING their work is well documentated are second rate rather than top rate developers. The work of the technical writer needs to influence development at the design stage! It does not matter whether the developer does or does not write the the documentation but it does matter whether the developer is COMIITED to both ensuring that there is proper documentation AND that the documentation process is an integral part of the development process that influences its outcome. They may write a rough outline but it's the technical writers who actually do the documentation. The outline for user documentation needs to be structured BEFORE development begins NOT as an afterthought. In a well structured development environment documentation is part of DESIGN not post design implementation . That is because thinking about end user at the design stage is necessary if the outcome of the process is going to be user centric. The problem is finding people with technical writing skills who are interested in helping with FreeBSD. Freebsd needs to reorganize the way it develops if it is going to interest techn ical writers. No technical writer wants to be associated with writing documnets for developments that have been poorly designed for the end user. Clearing up someone else's mess is no fun. If you treat technical writers as people who come along afterwards and pick up yopur trash OF COURSE you will not get them involved. You need to ask WHY it is difficult to get them. It is because freebsd does not produce software with a focus on end user satisfaction. This is a chicken and egg problem that can only be solved by a fu8ndamental shift both the focus of development objectives and the development process. It's also worth noting that a number of FreeBSD developers are not native English speakers. It's probably unreasonable to expect them to write polished English documentation. What I have found works in development is to create team relationships that cover design, development and documentation. I agree that this is a good approach. It's similar
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, 08 Dec 2005 14:15:48 +0100 Ivan Voras [EMAIL PROTECTED] wrote: You could use graid3(8) - it has data+parity components like raid5. What about write performance? Based on RAID3 documentation I have read (on the 'net, so I cannot vouch for the correctness of it), you will get worse write performance than with RAID5. Does anybody have some real numbers here? I've been using it for more than a year now and didn't have problems with it. Didn't have to try recovery from a dead disk also, but should work ok. I would prefer a firsthand crash report that tells what happened, and a step-by-step here's how I fixed it guide, but ok. :-) -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pw groupdel misbehavior?
Hello, Right now I submitted a problem report with a suggestion for a patch concerning this. It has the internal identification `bin/90114'. Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, Dec 08, 2005 at 02:31:00PM +0100, Stijn Hoop wrote: On Thu, Dec 08, 2005 at 12:18:57AM +0100, Torfinn Ingolfsen wrote: I was thinking about gvinum for the storage server, but given the current documentation and the discussions about it now, I don't want to risk it. IMHO it's pretty stable in 6.0. I've been running gvinum RAID-5 for a while now; other than one strange panic (something to do with out of memory situations, see kern/89660) I haven't had a hitch yet. That said, I haven't needed to replace a disk yet either (I've demoed this but it was not yet needed in production use). In short, don't write gvinum off just yet. Documentation is around the corner (as a result of a SoC project). Actually gvinum(8) has been committed to CURRENT and RELENG_6 a couple of days ago. - Christian -- Christian Brueffer [EMAIL PROTECTED] [EMAIL PROTECTED] GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D pgp4XVVYLawMp.pgp Description: PGP signature
Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
secmgr wrote: Doug Barton wrote: + When upgrading from one major version to another, it is + generally best to upgrade to the latest code in the branch + currently installed first, then do another upgrade to the + new branch. Or as another poster said, just say latest RELENG_5 prior to upgrade Based on recommendations from this thread and from kris, I changed the wording to be more generic, and added the same text to the UPGRADING file in HEAD, and RELENG_6. Well, if it's common knowledge, lets see it documented. We're only talking a few lines in the handbook or the release notes, not an entire chapter. I did my bit. I'm sure that the freebsd-doc folks are eagerly anticipating your patches, since this is such an easy thing to add. :) rant3 My frustration comes from the fact that this seems to be getting worse, not better. From your perspective that may be true, however from a more general perspective I don't agree. C'est la vie. In addition, every time I bring this up, I'm told (usually by someone with a freebsd.org address) that, oh we all know/knew about that or, it's common knowledge. I have been very careful to say that I agree that our documentation can always be improved. I've also been very careful to say that the only way this will happen is if someone steps up to do it. I realize that's not the answer you're looking for, but it's the only one we have, and all the elegantly phrased rants, descriptions of what we should be doing for you (and how we should be doing it), and other things that you (pl.) wish were so won't change that. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 as storage server with raid5?
On Thu, Dec 08, 2005 at 08:30:33PM +0100, Torfinn Ingolfsen wrote: On Thu, 08 Dec 2005 14:15:48 +0100 Ivan Voras [EMAIL PROTECTED] wrote: You could use graid3(8) - it has data+parity components like raid5. What about write performance? Based on RAID3 documentation I have read (on the 'net, so I cannot vouch for the correctness of it), you will get worse write performance than with RAID5. Does anybody have some real numbers here? I've been using it for more than a year now and didn't have problems with it. Didn't have to try recovery from a dead disk also, but should work ok. I would prefer a firsthand crash report that tells what happened, and a step-by-step here's how I fixed it guide, but ok. :-) It is REALLY FAST! Make sure you use 6.0-RELEASE or later so that you have the fix for lock-ups in certain usage patterns and also configure it for performance with graid3 label -r. -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdtar / libarchive bug?
On Thu, Dec 08, 2005 at 05:29:06PM -, Steven Hartland wrote:
It seems bsdtar can create files it cant read. i.e. it will happily create
empty tar.gz files but when it comes to read them the following error
is output:
tar: Unrecognized archive format: Inappropriate file type or format
Having a look at libarchive shows the following code:
/* An empty archive is a serious error. */
if (bytes_read == 0) {
archive_set_error(a, ARCHIVE_ERRNO_FILE_FORMAT,
Empty input file);
return (ARCHIVE_FATAL);
}
Which is where I expect the issue is, why would an empty archive
be fatal? I can see any reason for this, yes its strange but there's
nothing fatal about it imo.
I don't think it will happily create empty tar.gz files, even where
by empty you mean the tar itself inside of the gz.
{/home/green [EMAIL PROTECTED] tar cfv x.tar
tar: no files or directories specified
{/home/green [EMAIL PROTECTED] tar cfvz x.tar.gz
tar: no files or directories specified
{/home/green [EMAIL PROTECTED] ls -l x.ta*
ls: x.ta*: No such file or directory
--
Brian Fundakowski Feldman \'[ FreeBSD ]''\
[EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own. \,,\
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdtar / libarchive bug?
In the last episode (Dec 08), Brian Fundakowski Feldman said:
On Thu, Dec 08, 2005 at 05:29:06PM -, Steven Hartland wrote:
It seems bsdtar can create files it cant read. i.e. it will happily create
empty tar.gz files but when it comes to read them the following error
is output:
tar: Unrecognized archive format: Inappropriate file type or format
Having a look at libarchive shows the following code:
/* An empty archive is a serious error. */
if (bytes_read == 0) {
archive_set_error(a, ARCHIVE_ERRNO_FILE_FORMAT,
Empty input file);
return (ARCHIVE_FATAL);
}
Which is where I expect the issue is, why would an empty archive
be fatal? I can see any reason for this, yes its strange but there's
nothing fatal about it imo.
I don't think it will happily create empty tar.gz files, even where
by empty you mean the tar itself inside of the gz.
{/home/green [EMAIL PROTECTED] tar cfv x.tar
tar: no files or directories specified
{/home/green [EMAIL PROTECTED] tar cfvz x.tar.gz
tar: no files or directories specified
{/home/green [EMAIL PROTECTED] ls -l x.ta*
ls: x.ta*: No such file or directory
I managed to make it create 0-byte files:
$ touch a
$ tar cvf b.tar --exclude a a
$ tar zcvf b.tar.gz --exclude a a
$ ls -la b.tar*
-rw-r--r-- 1 dan wheel 0 Dec 8 17:37 b.tar
-rw-r--r-- 1 dan wheel 20 Dec 8 17:37 b.tar.gz
$ gunzip -vl b.tar.gz
method crc date time compressed uncompr. ratio uncompressed_name
defla Dec 8 17:3720 0 0.0% b.tar
This works because at the time tar creates the output file, it doesn't
know that I have excluded all the listed files.
I am leaning towards an empty archive being legal, though, since it
makes scripting easier. There may be cases where you are archiving
files generated daily, and you want to distinguish no data today from
the archiver didn't run. At worst it should print a warning.
--
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
[dhclient] connection closed, exiting
I have a Sun Ultra5 as my home gateway. After upgrading to 6.0 from 5.4 I started getting problems with dhclient (I know it went from v3 to v2 imported from OpenBSD) If my cablemodem dies without signal or something of the sort dhclient exits like this: Dec 8 18:38:24 ultra5 dhclient[198]: connection closed Dec 8 18:38:24 ultra5 dhclient[198]: exiting. Some cablemodems reset the ethernet interface on their bootup or sync sequence but since the machine is connected to a switch I take it it's not an interface connection we're talking about. On 5.4 I could kill the modem for hours and dhclient would stay there (as it should) trying to get a lease. On 6.0 I just have to silence the modem for a few moments and dhclient gives up and goes away. I couldn't find a knob for this on the manual. Sometimes it gets even better, when dhclient has saved (but already expired leases) and uses them setting the IP on the interface, but since the IP is not valid it doesn't work. And it stays with that lease until I restart it and it gets a valid one. I had signal problems the last few days and the leases db it's like this: ultra5# grep lease /var/db/dhclient.leases.fxp1 | wc -l 10 How can I: - tell dhclient not to exit. - tell dhclient not to use expired leases, or not to use saved leases at all. -- Joao Barros ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdtar / libarchive bug?
On Thu, Dec 08, 2005 at 05:45:40PM -0600, Dan Nelson wrote:
In the last episode (Dec 08), Brian Fundakowski Feldman said:
On Thu, Dec 08, 2005 at 05:29:06PM -, Steven Hartland wrote:
It seems bsdtar can create files it cant read. i.e. it will happily create
empty tar.gz files but when it comes to read them the following error
is output:
tar: Unrecognized archive format: Inappropriate file type or format
Having a look at libarchive shows the following code:
/* An empty archive is a serious error. */
if (bytes_read == 0) {
archive_set_error(a, ARCHIVE_ERRNO_FILE_FORMAT,
Empty input file);
return (ARCHIVE_FATAL);
}
Which is where I expect the issue is, why would an empty archive
be fatal? I can see any reason for this, yes its strange but there's
nothing fatal about it imo.
I don't think it will happily create empty tar.gz files, even where
by empty you mean the tar itself inside of the gz.
{/home/green [EMAIL PROTECTED] tar cfv x.tar
tar: no files or directories specified
{/home/green [EMAIL PROTECTED] tar cfvz x.tar.gz
tar: no files or directories specified
{/home/green [EMAIL PROTECTED] ls -l x.ta*
ls: x.ta*: No such file or directory
I managed to make it create 0-byte files:
$ touch a
$ tar cvf b.tar --exclude a a
$ tar zcvf b.tar.gz --exclude a a
$ ls -la b.tar*
-rw-r--r-- 1 dan wheel 0 Dec 8 17:37 b.tar
-rw-r--r-- 1 dan wheel 20 Dec 8 17:37 b.tar.gz
$ gunzip -vl b.tar.gz
method crc date time compressed uncompr. ratio uncompressed_name
defla Dec 8 17:3720 0 0.0% b.tar
This works because at the time tar creates the output file, it doesn't
know that I have excluded all the listed files.
I am leaning towards an empty archive being legal, though, since it
makes scripting easier. There may be cases where you are archiving
files generated daily, and you want to distinguish no data today from
the archiver didn't run. At worst it should print a warning.
Just don't let it accept a 0-length gzip.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''\
[EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own. \,,\
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 as storage server with raid5?
Christian Brueffer wrote: On Thu, Dec 08, 2005 at 12:18:57AM +0100, Torfinn Ingolfsen wrote: In short, don't write gvinum off just yet. Documentation is around the corner (as a result of a SoC project). Actually gvinum(8) has been committed to CURRENT and RELENG_6 a couple of days ago. - Christian Whatever you do, don't complain about it on this list, or you'll just be told that if you really wanted raid, you should be running SCSI disks and a raid adapter. They may allow that 3ware does ok, but no ATA drive should ever be relied on and even s/w raid on scsi is only for ignorant lusers who are too cheap to do the right thing. Those who think I run to hyperbole need only visit the archives. One can only hope that gvinum actually works in 6 vs the buggy and incomplete alpha code that shipped in 5.x. Having a man page is nice, but I'd rather have a raid 5 set that didn't panic the system and corrupt the set when it lost a drive (and this with modern scsi drives and adapter). I'd strongly suggest anyone using GEOM raid to do some fault insertion testing of their setup prior to actually relying on it. jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [FreeBSD 6.0-RELEASE] Incorrect geometry for VIA RAID0 array
On freebsd-stable, [EMAIL PROTECTED] (Jason Harmening) wrote: Here's the dmesg output from the installer: ad4: 70911MB WDC WD740GD-00FLA1 27.08D27 at ata2-master SATA150 ad6: 70911MB WDC WD740GD-00FLC0 33.08F33 at ata3-master SATA150 ar0: 70911MB VIA Tech V-RAID RAID0 (stripe 64 KB) status: READY ar0: disk0 READY using ad4 at ata2-master ar0: disk1 READY using ad6 at ata3-master Are you _sure_ that the array is being recognized properly? Based on the dmesg output, it looks like the controller is being read as a 74G drive. FWIW, this is the section of my dmesg output, for a _mirror_: ad4: 78167MB Maxtor 6Y080P0 YAR41BW0 at ata2-master UDMA133 ad6: 78167MB Maxtor 6Y080P0 YAR41BW0 at ata3-master UDMA133 ar0: 77247MB Promise Fasttrak RAID1 status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master On 12/7/05, Jason Harmening [EMAIL PROTECTED] wrote: I'm trying to install FreeBSD 6.0-RELEASE on a RAID0 array attached to the VIA 8237 controller on my Asus A8V Deluxe motherboard. The array consists of two 74G drives. The installer recognizes the array as ar0, but when I enter FDISK to set up my partition, the size of the array is only recognized as 74G, rather than the true 148G. I've double-checked all my BIOS settings, and nothing seems out of order. Please help! -- greg byshenk - [EMAIL PROTECTED] - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 as storage server with raid5?
Whatever you do, don't complain about it on this list, or you'll just be told that if you really wanted raid, you should be running SCSI disks Ah, no please complain so that if s/w raid gives you trouble, there will be something to point to when and if people doubt there are still problems (if indeed there are) Though I think jim is being entirely too harsh: The scary, poorly tested part of software raid is recovery. Thousands might roll out a s/w raid but if the h/w raid wasn't cost justified its unlikely that the HDs in the raid are actually going to be pressed into failing in any reasonable period of time that would reveal trouble in the recovery/degraded operating modes. Second, if you use s/w raid, pay close attention to the way your partitions line up. Third, SATA drives are actually quite good. You're primarily looking at a degraded MTBF versus a server grade SCSI disk. This could well mean just about nothing if your transaction volume is actually pretty low. imo, it would be nice to see MTBF quoted in a few parts: MTBF while seeking regularly (i.e., at some duty cycle) and MTBF in the bearings and other rotational components alone (MTBF while the disk is spun-up), and number of spin-up/spin-down cycles. Fourth, the major limitations on SATA drives right now is that FreeBSD does not support NCQ and therefore has no access to reliable write-completion information wrt SATA drives. and adapter). I'd strongly suggest anyone using GEOM raid to do some fault insertion testing of their setup prior to actually relying on it. This is very good advice. -Jon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Data Loss with samba shared USB drive
On Sat, Dec 03, 2005 at 09:46:05PM +, David Taylor wrote: On Sat, 03 Dec 2005, David Taylor wrote: I have a USB drive (SanDisk 1GB flash drive), which I have mounted on a windows PC using samba 3.0. I recently discovered the copy of my files on my USB device were corrupted (thankfully I had a backup), being filled entirely with 0's (that's ASCII '0', not NUL). I have managed to reproduce the problem with these steps. 1. Mount USB drive on (say) /usb 2. Share /usb over samba 3. (Optional) On windows PC mount \\server\usb as (say) U: 4. Change something on /usb drive (from windows or freebsd) 5. On FreeBSD machine type umount /usb -- get Device busy error 6. View changed file. I should probably mention that this is with the drive formatted with a FAT filesystem. Do you also know that nothing has /usb or a subdirectory of it open as a current working directory, and that no files are open? You're saying that the umount fails and the file also turns out to be corrupted, right? -- Brian Fundakowski Feldman \'[ FreeBSD ]''\ [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,\ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mcast-tools make my 6.0-STABLE kernel panic
Hi, On Thu, 8 Dec 2005 19:01:41 +0700 [EMAIL PROTECTED](Dikshie) said: and then I installed mcast-tools from ports/net when I try to run pim6sd I got kernel panic. panic: register_mif0: BUG: if_attach called without if_alloc'd input() I've committed the fix to -current. Could you please try the latest ip6_mroute.c in the -current? (There is no difference between -current and 6-stable except for the fix. So it is safe to use the ip6_mroute.c in -current for 6-stable. But you feel it awkward, please wait until I merge it to RELENG-6 in a few days) Thanks, SUZUKI, Shinsuke @ KAME Project ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
