WRONG
#
Feels...hosed
On Mon, Apr 27, 2020 at 12:17 PM Christos Zoulas
wrote:
> In article <
> caoax04pbwg4p2cq31v0gz7mpza7bc-jrvc2fusdojl-wgof...@mail.gmail.com>,
> Michael Cheponis wrote:
> >-=-=-=-=-=-
> >
> >I plugged in a 10TB USB disk, was work
I plugged in a 10TB USB disk, was working fine, then today it got weird.
*# ls /t>▒x4S▒▒XWе▒3▒▒Hj▒▒l▒▒gw,▒=▒&▒X▒▒צA▒▒▒B▒w l: Invalid argument*
*# umount -f /t*
*# fsck -f -tffs /dev/dk0** /dev/rdk0** File system is already clean** Last
Mounted on /t** Phase 1 - Check Blocks and
ion (limited in size because with
>the amount of memory here and the programs it runs, there should have
>been far enough).
Why do you think so?
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
ge (with GPT).
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
ry short time. But again, that
> is not what defines hard real time.
>
> If you get into a discussion with someone else, and that someone else
> says Unix can't do hard real time, he is still correct, no matter how
> much you fiddled around with your RPi.
>
>Johnny
>
Thanks to all who contributed here, I'm learning a lot.
As to what is 'real time' -- as you can probably tell by watching the video
at the URL, the robots were dynamically stable - they had to react within a
millisecond (Read sensors; do all control; storage of data for post-run
analysis, run all
elated.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
Is there already a way to do "hard real time" on NetBSD?
To me, "hard real time" means from an external pin going 'high' to the 1st
instruction of my driver executing is on the order of (up to) 10 usec.
Many eons ago, I did this on BSD4.3 VAX 785 and achieved < about 100 usec
jitter. It was a
e -
some rectangle fills never complete, the driver waits, times out,
resets the blitter, moves on. The visible symptom is X eating up
ridiculous amounts of CPU time.
have fun
Michael
76nem...@gmx.ch (Pierre Dupond) writes:
>Apr 8 12:01:12[949] Load /usr/X11R7/lib/X11/fonts/misc/8x16.pcf.gz (id 61)
>Apr 8 12:01:12[949] Failed to open pty
Do you have ptyfs mounted ?
--
--
Michael van Elst
Internet: mlel...@serp
choice of the proprietary (binary only) driver
from NVidia.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
usr/local.
You need a Linux emulated apache. You probably installed one of the
emulators/suse* packages, an apache binary from that suse release might
work.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential
ce does not work. Bad interrupt routing can be
an easy explanation, but difficult to fix.
Please try to capture the boot dmesg (saved as /var/run/dmesg.boot) so
that someone can look at it.
--
--
Michael van Elst
Internet: mlel...@serpens.de
ured for openssl.
>It is 2020. I am a firm believer the tools should do the work for me.
>I don't work for the tools.
Other people believe that tools should not make decisions for you,
instead they should give you choices.
There is probably a middle ground.
--
--
che and doesn't work, there are
other problems. Maybe apache prints some error messages that
give a hint.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
lect an input source or to set input gains or to mute individual inputs.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
, then each thread opens a descriptor and shares it for the
SSL sessions created from that thread.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
fr...@phoenix.owl.de (Frank Wille) writes:
>Michael van Elst wrote:
>> I think the only option you have now is to prevent access to /dev/crypto.
>Confirmed! I renamed /dev/crypto and all the 200+ file desciptors per
>apache process are gone. Horde also feels snappier again and t
efault sizes, but in your case the program sets the value.
nmbclusters is the space where all socket buffers are allocated from.
Even with one UDP socket buffer of 4MB the default should be enough,
otherwise increase it carefully. Each nmbcluster is 2kB,
--
--
Mich
"config.h" and included only
after "util/mini_event.h". That's too late.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
ly
loaded it would work, but since it is builtin, it opens /dev/crypto
right from the start.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
nk the only option you have now is to prevent access to /dev/crypto.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
? What can I do (besides
>restarting Apache or the whole server)?
Something is using /dev/crypto. openssl would do that, but only if
you configure it.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
to generate the input.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mar...@duskware.de (Martin Husemann) writes:
>> Why the use of the raw device makes a difference.
>It avoids another level of buffering in the kernel.
The block device also uses tiny 2KB requests that are extra slow
for SD cards.
--
--
Michael
n xen load kernels in multiboot
>way or NetBSD xen kernels have this ability?
It's not the xen kernel that takes the root= parameter. But yes,
that's very MD specific how boot parameters can be passed.
--
--
Michael van Elst
Interne
device named dk1. You could specify it
as a major/minor combination like:
config netbsd root on major 168 minor 1 type ?
or use a string with a device name
config netbsd root on "dk1" type ?
or use a string with a wedge name like above.
--
--
eriments on that.
have fun
Michael
I think it would be good to explain how to set it up on NetBSD -at least
for x64 and x86.
Specifically; tell people to put zfs=YES in rc.conf, then give
instructions on how to create some pools, and then point to the oracle
docs for more on zfs.
Although it might be better to point to
t comment
out the wedge scanning in the wd driver.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
mar...@duskware.de (Martin Husemann) writes:
>On Sat, Feb 29, 2020 at 09:41:46PM -0000, Michael van Elst wrote:
>> From the description it looks like he is using ataraid (ld0) and
>> also sees the components (wd0 and wd1).
>Duh. Can't the ataraid driver detect this and mark/bl
mount
...
data on /disk type zfs (NFS exported, local)
That's it. I ran a full build.sh release on it with no problems. No
need to mess with fstab, zfs=yes will take care of it.
have fun
Michael
the controller
is in RAID mode. If the RAID attachment then fails, you would
end with no wedges scanned at all. In this case you need to
trigger the scan on the components. Not sure how to do this safely.
A workaround is of course to migrated to raidframe.
--
--
t;> #2 0x80a40299 in vpanic ()
>> #3 0x80a4035d in panic ()
>> #4 0x8022669d in trap ()
>> #5 0x8021ed43 in alltraps ()
>> #6 0x80abd3bf in spec_read ()
Got it. specfs relies on a sanitized pi_bsize value.
I've updated the patch. Ple
t it, you can still do (from the same sources) and use it to
analyze the core file.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
On Fri, Feb 28, 2020 at 02:12:29PM +, Chavdar Ivanov wrote:
> On Thu, 27 Feb 2020 at 20:41, Michael van Elst wrote:
> > I've prepared a patch for -current that fixes this issue.
> > http://ftp.netbsd.org/pub/NetBSD/misc/mlelstv/zvol.patch
>
> After applying
mlel...@serpens.de (Michael van Elst) writes:
>mlel...@serpens.de (Michael van Elst) writes:
>>ci4...@gmail.com (Chavdar Ivanov) writes:
>>># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>>>ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
>
mlel...@serpens.de (Michael van Elst) writes:
>ci4...@gmail.com (Chavdar Ivanov) writes:
>># ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>>ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
>>Apparently not, in this case. I think the comments in
iver can use a regular block device as
component and present the result as a disk. Something must be different
with a zvol or your system. In any case, the errno value (ENOTTY)
is bogus as CCDIOCSET is perfectly valid for the ccd driver.
--
--
Michael van Elst
In
te and the boot process shouldn't
abort when the server fails.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
d0[a-p]
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
omponent, it again presents the result as a partitioned
disk.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
nting (vnd0a or vnd0d) and get =E2=80=9Cincorrect superblock=E2=
>=80=9D errors.
It should work by accessing the raw disk vnd0d (and works here).
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
e redirected with the TIOCCONS ioctl. That's how
xconsole works, it opens a pty, redirects console output to it
and then logs things written to the pty to an X window.
sysinst could do the same and then e.g. present console output in a
curses window.
--
--
Michael van E
ssed by a driver. I guess it's less power saving but more trying
to trigger Windows to install a missing driver.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
I haven't tested it extensively, but I'm able to load zpools I created
in NetBSD on Debian 10 and on Centos 8.
On 2/24/2020 10:16 AM, Rocky Hotas wrote:
Hi all!
ZFS is one of the major updates in NetBSD 9.0. As far as I understood,
it is an implementation of OpenZFS, as Linux and FreeBSD
ore
> > compatible.
>
> Same configuration files or not ?
Unfortunately not.
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
itrary sized buffer.
In my experience the iscsi target (and the userland iscsi initiator)
are pretty limited and somewhat broken. I suggest you use the
iscsi target from pkgsrc (net/istgt). Much better, faster and more
compatible.
--
--
Michael van Elst
In
On 2/19/2020 9:51 PM, Clay Daniels wrote:
On Wed, 19 Feb 2020, Clay Daniels wrote:>
I have found that the only way it works for me is to use MBR. not
GPT. Anyone have any luck with a GPT installation?
To answer my own question, it makes sense to run NetBSD on MBR as
NetBSD's default
a tiny example that is different from the default. Few
people stay with the default, they either adapt it or have a private
.xinitrc (or .xessionrc if you use xdm instead of startx).
>All in all, I'm having fun with this new NetBSD 9.0.
Good to hear :)
--
--
Michael va
On 2/17/2020 1:37 AM, Chavdar Ivanov wrote:
On Mon, 17 Feb 2020 at 10:17, Michael Huff wrote:
Hi
I'm playing with netbsd on virtualbox. Because NetBSD can't boot from
ZFS (for now) I have two disks; a small one for the system and a larger
one to put zfs and other things on.
I've figur
Hi
I'm playing with netbsd on virtualbox. Because NetBSD can't boot from
ZFS (for now) I have two disks; a small one for the system and a larger
one to put zfs and other things on.
I've figured out how to create and destroy pools and datasets; but I
haven't been able to figure out how to
michael.chepo...@gmail.com (Michael Cheponis) writes:
>dtc -I dtb -O dts bcm2710-rpi-3-b-plus.dtb does produce similar output as
>you mention.
But only similar. Check the 'status' line for each entry, it probably
says 'disabled' and not 'okay'.
You can either modify the DTB or add overlay
is not finding any i2c bus.
On Wed, Feb 12, 2020 at 1:41 PM Michael van Elst wrote:
> michael.chepo...@gmail.com (Michael Cheponis) writes:
>
> -rwxr-xr-x 1 root wheel 22630 Jun 16 2019 bcm2837-rpi-3-b-plus.dtb*
>
> > Raspberry Pi 3 Model B Plus Rev 1.3 - so I'm not sure which of the
michael.chepo...@gmail.com (Michael Cheponis) writes:
-rwxr-xr-x 1 root wheel 22630 Jun 16 2019 bcm2837-rpi-3-b-plus.dtb*
> Raspberry Pi 3 Model B Plus Rev 1.3 - so I'm not sure which of the
>highlighted dtb files is used.
That one would have i2c enabled. You can disassemble the dtb
seem
to have i2c* entries.
Thanks for all help.
On Wed, Feb 12, 2020 at 12:01 AM Michael van Elst
wrote:
> michael.chepo...@gmail.com (Michael Cheponis) writes:
>
> >Hi all, I want to hook up a sensor using iic on an RPi. Is there a
> >tutorial somewhere on how to do this?
michael.chepo...@gmail.com (Michael Cheponis) writes:
>Hi all, I want to hook up a sensor using iic on an RPi. Is there a
>tutorial somewhere on how to do this? Do I have to compile a specific
>config to enable iic because GENERIC doesn't?
netbsd-9 has it defined in GENERIC and the
Hi all, I want to hook up a sensor using iic on an RPi. Is there a
tutorial somewhere on how to do this? Do I have to compile a specific
config to enable iic because GENERIC doesn't?
I tried this:
*# i2cscan iic0
i2cscan: couldn't open iic0: Device not configured# i2cscan iic1
min of the company backup system may still be able to read your files.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
65536 (128MB).
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
ut it's unclear whether that's safe.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
ch all unused disks when booting, e.g.
by calling something like 'drvctl -d sd1' in /etc/rc.local.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
be confused with
a FAT filesystem. exFAT is something completely different.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
byte sectors
this is 2TB. A single file has a limit of 4GB.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
FAT filesystem when you tag the
partition as MSDOS. Since the original type (from MBR) was NTFS it
is probably an NTFS filesystem.
But you can now format sd0e as FAT filesytem with newfs_msdos (deletes
all data) and then mount it.
--
--
Michael van Elst
Internet: mle
rtunately nobody needed
to care about the details, the cards were just replaced.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
sv2 for new filesystems, in case the extra
features become relevant. If it's not too much work I would recreate
the filesystem.
Greetings,
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
by augmenting
/etc/sysctl.conf with
ddb.onpanic?=1
It's not always possible to write a kernel dump and you need a swap
partition that is large enough. From ddb you can try the command
"sync", but if it doesn't dump automatically it probably won't work
from ddb either.
--
--
ver that emulates a tty
interface but uses a proprietary protocol when talking to the device.
Since NetBSD lacks such a driver, the device attaches as 'ugen', so you
could do low-level USB operations yourself via /dev/ugen0.00 (.. ugen0.15)
if you knew that proprietary protocol.
--
--
ilesystem blocks will be in exactly one CF block.
- mount your filesystems with noatime and nodevmtime
- put /tmp and /var/tmp in a tmpfs
- make sure you've got enough RAM so you don't need/use swap space
have fun
Michael
cite'.
> Do you have any suggestion?
I'm using joe for text mode and bluefish in X. Bluefish is supposedly
made for web development but it supports all sorts of languages with a
filesystem tree in a side panel, which is extremely useful when working
on kernel code.
Both do syntax highlighting and all sorts of other stuff.
have fun
Michael
has :)
Some drives do not have SMART enabled by default. You can change that
with the atactl command, but some drives only then start to collect
statistics.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
need to move things over to the Hitachi hard drive, including
>user data that could not be reinstalled.
Backing up the data is of course the first thing. But please also check
the disk with smartmontools or 'atatctl wd1 smart status' to see if itself
reports problems.
--
--
amd64, but apparently not with
>NetBSD 7.99.1 (an old installation) or FreeBSD.
A timeout can have many causes, but here I suspect some issue with NCQ.
Try to disable NCQ for that drive with
sysctl -w hw.wd0.use_ncq=0
--
--
Michael van Elst
Int
one of the caveats matter, some free space comes handy, e.g. if
you want to keep multiple kernels or a multi-boot environment.
Greetings,
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
pr...@cam.ac.uk (Patrick Welche) writes:
>gpt add -a 4k -l efi0 -s 525256 -t efi wd0
With 2 FATs.
4 + 64 * 2 + 65525 * 1 = 65657 4k sectors (or 525256 0.5k sectors).
--
--
Michael van Elst
Internet: mlel...@serpens
096 free (65524 clusters)
One cluster (one sector) is already used by the root directory.
The 65525 cluster minimum is pretty artificial because FAT16 is
good enough for up to 65524 clusters.
More at:
https://en.wikipedia.org/wiki/Design_of_the_FAT_file_system
--
--
M
0 0# (Cyl. 0 - 1399)
You can then use /dev/vnd0a to mount the filesystem.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
illator is used.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
this is EINVAL.
atabus has multiple attachment points. You need to rescan with
the attribute ata_hl, i.e:
drvctl -r -a ata_hl atabus1
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
bridge enabled for you.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
tlaro...@polynum.com writes:
>2) Is there a way to query the status of the disk in order to give a hint
>to the user about if it's safe or not to unplug the external device?
It is safe to unplug the device when you have unmounted the filesystem.
--
--
M
d also calculate the offset and size of the partition inside the RAID
volume and manually add a wedge with these parameters.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
e for recovery?
https://lists.freebsd.org/pipermail/freebsd-questions/2016-May/271785.html
has a list of tools that may help to recover data.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
e attribute
storage.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
ts fragments,
not physical disk blocks, the effective limit for the filesystem size
varies between 1TB (512byte fragments) and 128TB (64kByte fragments).
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
issymmetry and fallback so it's approaching what I was looking fo.
That's the FreeBSD variant of Linux DRBD. A very regular RAID where one
part is on a remote machine.
And no, we don't have something like it.
--
--
Michael van El
gt; kern.timecounter.hardware = hpet0
>and things seem ok, at least after 10 minutes.
That's what to do, you can also use the ACPI timer.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
2048 on a 16GB drive
isn't that common, it's probably correct.
A synthesized disklabel would match the MBR, so that one has probably
been written to the USB drive.
Can you try to erase the label with 'disklabel -D sd0' ?
--
--
t typed as "swap" or "raid".
The swap code ignores the type, but the dump code does not.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
works fine in 15m
distance from the access point.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
to give you information about the disk, and so
is part of the filesystem superblock. Providing inconsistent fake information
won't work.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
od, but it won't help with the bootloader problem
either.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
m the EFI partition instead by putting
a configuration into /EFI/NetBSD/boot.cfg.
N.B. I haven't actually tried this.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
t, this has different
issues but works around the limits of the NFS design.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
re occupied with a real-time process or interrupt handler. But
I doubt that his is happening here...
None of these _should_ block forever but time out eventually which may
take some time, but you _should_ also see error messages on the console.
Greetings,
--
Mic
br...@nmsu.edu (Brook Milligan) writes:
>> On May 13, 2019, at 3:43 AM, Michael van Elst wrote:
>>
>> br...@nmsu.edu (Brook Milligan) writes:
>>
>>> # ps -lp 4904
>>> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TTYTIME COMMAND
>>>
be done (short of a power reset) to unwedge this machine?
Probably nothing.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
On Tue, Apr 23, 2019 at 10:01:24PM +0530, Mayuresh wrote:
> On Tue, Apr 23, 2019 at 03:55:41PM -0000, Michael van Elst wrote:
> > The display is handled by the firmware, depending on your HDMI display
> > you need to configure overscan in /boot/config.txt.
>
> I had a feel
overscan in /boot/config.txt.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
301 - 400 of 670 matches
Mail list logo
