Re: Autoconfigured RAIDframe raid* numbering
Hi, On Thu, Sep 02, 2021 at 02:43:00PM +0100, Patrick Welche wrote: > On Thu, Sep 02, 2021 at 03:36:50PM +0200, Edgar Fu? wrote: > > > > WARNING: findroot: double match for boot device (sd4, sd5) > > > > (where sd4a/5a are raid2's components) before > > > > boot device: raid2 > > > > root on raid2a dumps on raid2b > Doesn't that just mean that you could boot from sd4a or from sd5a > as they are the components of the boot raid2? I read it as such. Remember, our bootloader doesn't really understand raidframe; we're cheating. It only knows an additional offset, which happens (well, we did it un porpose) to be where a raid0 root partition is inside the raid disk's image on both (all) the component disks in a raid0 setup. As a consequence, the individual boot disks aren't hidden from the kernel. Regards, -is
Re: I think I've found why Xen domUs can't mount some file-backed disk images! (vnd(4) hides labels!)
On Sun, Apr 11, 2021 at 10:15:18PM -, Michael van Elst wrote: > I have also seen winchester disks with 128 byte sectors, ESDI > disks with 576 byte sectors and CD-ROM XA media uses 2352 byte > sectors. I've seen a washing machine sized DEC disk drive, formerly used by the Physics institute @ Bonn University's PDP-10 (don't know the exact type, one or two dozens of washing-machin-sized cabinets), using 128 word (36bit) blocks. When the PDP-10 was decomissioned, my (then) boss added it to "his" VAX11/750, reformatted with 512-byte sectors. -is
Re: Changing ether_ifattach() and ether_ifdetach() arguments to struct ethercom* ?
Hi Martin, I've re-read my notes[1] about introduction of ethercom when it replaced arpcom. I guess I kept the spirit of the old interface back then. One plus is that we COULD use it in a more abstract way (e.g. in a function table), but this isn't how we use it now and we somehow would need to abstract the second parameter. So I tend to not object to your proposed change. I notice, however, that you'd need to touch all ethernet (and, for symmetry, all FDDI) drivers. This is a lot of code. Wait, didn't we remove FDDI recently? so, a few less. But we didn't remove the reference from ethersubr(9). -is [1] https://web.archive.org/web/20020623184642/http://ezine.daemonnews.org/199809/underhood.html
Re: Brainy: Memory Leak in if_ieee1394
Hi,
On Sat, Jul 25, 2015 at 10:28:21AM +0200, Maxime Villard wrote:
> there is a memory leak here:
>
> --- sys/net/if_ieee1394subr.c --
...
> I think a correct fix would be:
>
> if (m->m_next == NULL) {
> m_freem(m);
> goto bad;
> }
Looks good to me.
-is
--
A medium apple... weighs 182 grams, yields 95 kcal, and contains no
caffeine, thus making it unsuitable for sysadmins. - Brian Kantor
vm_map hangs with netbsd-6
Hi, I'm experiencing situations, where my Shark, updated to 6.1.5, can't exec or fork or otherwise change the mappings of processes anymore. E.g. I start date in a pre-exsiting shell, and the process hangs in vm_map forever. Especially annoying is that killing other processes hangs, too, so the only fix is to hardware reset, including full fsck. Culprit is the kernel; same problem before updating userland! The machine was rock stable with netbsd-5.1.3 I've heard the suspicion that his is not Shark-specific, but applies to other small-vm-space (32bit) architectures, too; I've not seen it elsewhere. Ideas? [Actually, I would have rebooted into a -5 but I updated mistakenly userland, too... -is
Re: asymmetric smp
On Wed, Mar 26, 2014 at 07:32:24PM -0700, Matt Thomas wrote: > > I recently ordered an ODROID-XU Lite to help beat on the my ARM MP code. Ah... for a second I thought you want to add support for the VAX 11/782. -is
USB audio doesn't record 8bit? (or: play 8bit?)
Hi, on sysadm# uname -a NetBSD sysadm 6.0_RC2 NetBSD 6.0_RC2 (MONOLITHIC) #7: Thu Sep 27 16:44:58 CEST 2012 ignat...@random84.cs.uni-bonn.de:/var/itch/sources/6.0/oi386/sys/arch/i386/compile/MONOLITHIC i386 audio0 at uhub5 port 1 configuration 1 interface 0 uaudio0: vendor 0x0556 product 0x0001, rev 1.10/0.01, addr 3 uaudio0: audio rev 1.00 audio1 at uaudio0: full duplex, playback, capture, independent audiorecord doesn't record audioplay-able files in 8bit per sample modes, be it ulinear, slinear or u-law. 16bit linear and slinear works. playing 8bit-ulaw works. Has this been observed elsewhere? I seem to recall having had a similar problem on Shark long ago, but can't find the PR or e-mail message, if any. Regards, -is -- seal your e-mail: http://www.gnupg.org/
Re: hf/sf [Was Re: CVS commit: pkgsrc/misc/raspberrypi-userland]
Hi, On Tue, Nov 12, 2013 at 07:47:20PM +, Michael van Elst wrote: > m...@3am-software.com (Matt Thomas) writes: > > > >On Nov 11, 2013, at 10:08 PM, Michael van Elst wrote: > > >> The "slowdown" is already enormous due to lack of floating point > >> hardware. That's why emulating the FP hardware is a very common > >> way to handle this situation, just look at the other platforms. > > >The exception handling is much costlier than doing a softfloat call. > > You missed the second paragraph. > > >Its also adding kernel bloat. > > Indeed, a little bit of kernel bloat compared to a dozen userlands > and a dozen package repositories that require building and testing. Yes - I didn't measure current arms in that respect, but I did try to add the M68060 missing FP instruction emulation package to libm and compare to the kernel trap version a couple of years ago. The kernel trap version turned out to be faster - I guessed because of less (physically indexed) cache trashing. -is -- seal your e-mail: http://www.gnupg.org/
Re: Temporary IPv6 addresses vs. netgroups
On Mon, Jan 21, 2013 at 12:22:09AM +0100, Rhialto wrote: > I have set my laptop to use temporary random IPv6 addresses > (net.inet6.ip6.use_tempaddr=1). However, it also seems to use those when > trying to mount an NFS filesystem. Since NFS is basically authenticated > by address, the mount isn't allowed. (So in practice I force it to use > IPv4). > > How can I get some socket(s), in this case those from mount, to use the > normally assigned, non-random address? In general, bind(2) it before connect(2)ing. I notice no method to tell mount_nfs to do this... Regards, -is
Re: nfsd "serializing" patch
On Fri, Dec 07, 2012 at 08:42:39AM +, David Laight wrote: > With only one server process it is all fine. If all is backed by the same disk? Hm is
Re: Aborted Command, ahd_timeout, panic: no dir
Hi, On Mon, Nov 26, 2012 at 02:34:47PM +0100, Edgar Fuß wrote: > Can anyone make sense out of the following sequence of events (on 4.0, I have > to admit)? > After a reboot, sd0 didn't respond fully (i.e. the SCSI BIOS reported the > drive model, but not the capacity and one couldn't boot from it) until I > pulled out its SCA tray and re-plugged it. > After that, the machine came up fine. So the HBA was fully operational, but the disk didn't reset fully? Assuming the SCSI BUS reset code is in ahd is ok, I'd think about one of: - cable/connector not fully connected, broken wire/half-broken pin or similar (ahd does SCSI over parallel SCSI cable, right?) - disk didn't reset fully, and was in a half-wake electronic state. In the latter case, I'd consider the power supply capacity, among other sources of the problem. Hm, semi-brownout? -is -- seal your e-mail: http://www.gnupg.org/
Re: selectively disabling atime updates?
On Thu, May 31, 2012 at 08:37:06AM -0700, Paul Goyette wrote: > On Thu, 31 May 2012, Matthias Kretschmer wrote: > > >On Thu, May 31, 2012 at 04:42:27PM +0200, Edgar Fuß wrote: > >>>How about using fss for it instead. > >>1. fss is still marked experimental. > >oh, I have overlooked that. > > > >>2. does fss work with WAPL at all? > >I don't know that. > > It seems to work for me! All my FS are WAPBL-enabled, and I always > use backup -X for snapshot. rsync from a snapshot wouldn't work for me on sparc-64 with an oldish kernel (5.99.something). I must setup one of the slower machines for at least partial tests, because the main one is the file server... Paul, what's your architecture and version? -is -- seal your e-mail: http://www.gnupg.org/
Re: NetBSD on current AMD motherboards
On Tue, Jan 24, 2012 at 02:13:43PM +0100, Edgar Fuß wrote: > I wrote: > > So, are there any recommendations for current Opteron motherboards with good > > NetBSD support? > Since I didn't receive any specific suggestions, may I ask whether anyone is > running > NetBSD on either a Supermicro H8SCM-F or a Tyan S8010? Now that we have good power, I'm setting up on a Dell R310. Also running fine (but no fileserver duties): Sun X4140, 2x6CPU, as of... a while ago. -is
Re: Lost file-system story
On Tue, Dec 06, 2011 at 12:44:16PM -0500, Donald Allen wrote: > On Tue, Dec 6, 2011 at 11:58 AM, Thor Lancelot Simon wrote: > > On Tue, Dec 06, 2011 at 11:10:44AM -0500, Donald Allen wrote: > >> > >> 2. I'm a little bit surprised that the filesystem was as much of a > >> mess as it was. > > > > I'm not. You mounted the filesystem async and had a crash. With the > > filesystem mounted async *nothing* pushes out most metadata updates, > > with the result that the filesystem's metadata can quickly enter a > > fatally inconsistent state. The only way home safe is a clean unmount. > > So unwritten meta-data from an async filesystem can sit in the buffer > cache for arbitrarily long periods of time in NetBSD? I just want to > be sure I understand what you are saying. Because that essentially > guarantees, as you imply above, that if the system crashes, you will > lose the filesystem. That makes the following warning, in the mount(8) > man page, in the description of the async option: > > "In the event of a crash, it is impossible for the system to verify > the integrity of data on a file system mounted with this option." > > much more clear. When I read this before the fun started, I took it to You left out part of the warning. From NetBSD 5.1: async All I/O to the file system should be done asyn- chronously. In the event of a crash, it is impossible for the system to verify the integrity of data on a file system mounted with this option. You should only use this option if you have an applica- tion-specific data recovery mechanism, or are willing to recreate the file system from scratch. Isn't the last sentence of that paragraph in your version? Basically, there are two situations where -o async on ffs is sort of safe: a) you're installing or restore(8)ing on a freshly newfs'd filesystem, plan to unmount (or shutdown) as soon as you're finished before using the file system, and could do that again, with the same source data, in the event of a power failure during the operation; you get the benefit of a fast installation/restore. b) the file system is on volatile memory and would be gone anyway on shutdown, crash, or power failure. FFS in its default mode has been designed to do part of operations in an async fashion, but to guarantee enough writes that the remaining inconsistencies after a power failure can be cleaned up by fsck_ffs. fsck_ffs is designed for this task. It's not designed for arbitrary repairs. (When ffs does async, it really does it.) Regards, -is
Re: fs-independent quotas
On Thu, Oct 20, 2011 at 03:16:09PM +, David Holland wrote: > On Thu, Oct 20, 2011 at 11:57:04AM +0200, Ignatios Souvatzis wrote: > > > support to other filesystems (tempfs, perhaps v7fs) or even add other > > > filesystems that have or may have their own native quota handling > > > (zfs, Hammer, you name it). > > > > zfs - does it really have quota? > > I don't know... but if not, there are plenty of other fses. > > > All the demos I've seen talk about sub-filesystem limits; you create > > per-user sub-filesystems if you want to emulate per-user quota. > > > > (Correct me if I'm wrong.) > > > > How would this fit in, if at all? > > That's a good question. My first instinct is that like the other stuff > zfs does that it does in its own semantically-incompatible way, it > would require its own tools. But I guess the quota system could be > made to report the limits if the sub-filesystems are specifically > assigned to users somehow. Or something like that... The problem is that sub-file-system per user, or one per workgroup and one subsubfs per user, are only special cases of what you can do. It's really a filesystem, mounted at some point in the tree, and can be used to limit finer-grained than what you can express with user and group quota, although it can emulate their functionality. -is
Re: fs-independent quotas
On Wed, Oct 19, 2011 at 06:09:27PM +, David Holland wrote: > support to other filesystems (tempfs, perhaps v7fs) or even add other > filesystems that have or may have their own native quota handling > (zfs, Hammer, you name it). zfs - does it really have quota? All the demos I've seen talk about sub-filesystem limits; you create per-user sub-filesystems if you want to emulate per-user quota. (Correct me if I'm wrong.) How would this fit in, if at all? -is
Re: bug #44412
On Wed, Aug 03, 2011 at 04:41:01PM +0200, Thomas Klausner wrote: > On Fri, Jul 22, 2011 at 02:55:21PM -0400, David Riley wrote: > > I filed this report a while back. Someone else has tested my fix on > > non-PPC systems (x86, x86_64) and reported that it seems to work as well. > > I'm attaching the patch against -current here; could someone give it a look > > and include it if it seems to be OK? Or provide feedback if it doesn't. > > Thanks for the bug report and patch. > I'm not using netatalk and can't judge the patch; until someone comes > along that can, please add the patch to the bug report as well, so > it's not lost. I can look at this; I have an Appletalk printer in occasional production us. (but don't know whether I'll manage before I disappear for vacation, so yes, add to the PR.) Regards, -is
Re: ffs snapshots patch
On Fri, Apr 29, 2011 at 01:56:01PM +0200, Juergen Hannken-Illjes wrote: > On Fri, Apr 29, 2011 at 01:48:39PM +0200, Manuel Bouyer wrote: > > With your last changes, things are much better now: > > /usr/bin/time fssconfig fss0 /home /home/snaps/snap0 > > 149.85 real 0.00 user 1.16 sys > > /home: suspended 0.040 sec, redo 0 of 2556 > > /usr/bin/time fssconfig fss1 /home /home/snaps/snap1 > > 227.49 real 0.00 user 1.90 sys > > /home: suspended 0.040 sec, redo 0 of 2556 > > /usr/bin/time fssconfig fss2 /home /home/snaps/snap2 > > 263.58 real 0.00 user 2.97 sys > > /home: suspended 0.040 sec, redo 0 of 2556 > > /usr/bin/time fssconfig fss3 /home /home/snaps/snap3 > > 353.23 real 0.00 user 3.88 sys > > /home: suspended 0.040 sec, redo 0 of 2556 > > > > Taking a snapshot will still probably require a lot of time on > > large filesystems with a dozen snapshots, but at last the server > > won't hang for a long time. > > thanks ! > > Not really. Any thread ending up in ffs_copyonwrite() or ffs_snapblkfree() > will block. If this server runs NFS it could be possible that all NFS > server threads block. Oh - I might have seen this on Monday - 5.99.47 on sparc64. All I saw was [tstile], and the quickest way out after a couple of minutes was to hard reboot the machine and let wapbl / fsck sort it out - and to move back to the pre-snapshot rsync script. Sorry, no core dump. Regards, -is
bouyer-quota2: fsck_ffs crash
Hi, % unmount /export/home/1 % tunefs -q user /export/home/1 % fsck -fy /export/home/1 ... > USER QUOTA MISMATCH FOR ID 0: 0/0 SHOULD BE 1791988/1794 > ALLOC? yes > USER QUOTA MISMATCH FOR ID 0: 0/0 SHOULD BE 0/0 > ALLOC? yes > fsck: /dev/home/rtheory1: Segmentation fault This is on Sparc64. I'll provide more data tomorrow, assuming I'll find time to point gdb at a -g binary and the core dump. Regards, -is
Re: Is there a way to obtain a machine's cache line size?
On Thu, Jan 20, 2011 at 02:47:11PM -0500, der Mouse wrote: > > I see there is a compile time constant CACHE_LINE_SIZE in > > which currently seems to be always be set to 64, but > > I'm pretty certain that is not necessarily a correct value. > > You are correct; to cite the one example I currently have swapped into > my brain, the Super-H used in the Dreamcast has 32-byte cache lines > (true of the I-cache and D-cache both). m68060/68040/68030/.. I think and 68020 have all 16 bytes cache line size. m68010 doesn't have a real cache, but the very small instruction fetch fifo is blocked when a djnz is executed, so that a very short loop (1 other instruction) can be executed without repeated instruction fetches. -is
Re: radix tree implementation for quota ?
hi, On Sun, Nov 28, 2010 at 05:53:59PM +0100, Manuel Bouyer wrote: > Hello, > our FFS quota system is pretty outdated and is less and less suitable > for modern storage (quotacheck is long and can't be avoided). I'm thinking > about coding a new quota system with would be more closely integrated > with the filesystem, where quotas would be integrated with filesystem > metadata (maybe as part of a hidden indode, the same way WAPBL has a > inode for in-filesystem log). With this, quotas can be checked by fsck_ffs(8) > at almost 0 cost in time, and it can be covered by WAPBL, completely > eliminating the need for quotacheck(8) on reboot. uhm, but our current quota implementation - at least as described by the 4.3BSD paper - does that, only that the inode isn't hidden... > One open question is how to store quota informations on disk. > At this time we use one big array indexed by uid or gid. This can > be very space-consuming Why? It's a sparse file unless you copy it using cp. -is
Re: blocksizes
On Thu, Feb 04, 2010 at 12:15:15AM +0100, Michael van Elst wrote: > The original adosfs has been used on media with differnet block > sizes. That doesn't say anything about our implementation, but > different block sizes have been designed in from the beginning. I seem to recall having used adosfs on MO with 2048 bytes/sector from NetBSD. Regards, -is -- seal your e-mail: http://www.gnupg.org/ pgp5xxzHwndX0.pgp Description: PGP signature
Re: WD_QUIRK_FORCE_LBA48
About [LBA28 boundary crossing] Has something eben done about this? We have an error report on port-amd64. Regards, -is -- seal your e-mail: http://www.gnupg.org/
