On 22/02/2020 4:28 am, Sad Clouds wrote:
Hi, is it advisable to NOT enable log option for FFSv2 that resides on
SD card due to flash memory wearing out in those regions, or does it
make no practical difference because of built-in wear levelling?
How long's a piece of string?
Wear levelling
On Fri, Feb 21, 2020 at 07:46:26PM +0100, BERTRAND Joel wrote:
> > 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.
>
>
On Fri, 21 Feb 2020 at 19:29, Chavdar Ivanov wrote:
>
> On Fri, 21 Feb 2020 at 18:46, BERTRAND Joel wrote:
> >
> > Michael van Elst a écrit :
> > > joel.bertr...@systella.fr (BERTRAND Joel) writes:
> > >
> > >> If I understand... Error is triggered by test
> > >>
On 21/02/2020 18:10, Maxime Villard wrote:
Le 21/02/2020 à 10:57, BERTRAND Joël a écrit :
Maxime Villard a écrit :
Hi,
1) How much ram does your system have?
16 GB
2) If you add "#define NO_X86_ASLR" at the top of
sys/arch/x86/x86/pmap.c, does
the system boot fine?
I
On Fri, 21 Feb 2020 at 18:46, BERTRAND Joel wrote:
>
> Michael van Elst a écrit :
> > joel.bertr...@systella.fr (BERTRAND Joel) writes:
> >
> >> If I understand... Error is triggered by test
> >> /usr/src/netbsd-9/src/external/bsd/iscsi/lib/../dist/src/lib/disk.c line
> >> 1405 when initiator
Michael van Elst a écrit :
joel.bertr...@systella.fr (BERTRAND Joel) writes:
If I understand... Error is triggered by test
/usr/src/netbsd-9/src/external/bsd/iscsi/lib/../dist/src/lib/disk.c line
1405 when initiator sends data greater than 1MB.
Why this limitation ?
Apparently to avoid
joel.bertr...@systella.fr (BERTRAND Joel) writes:
>If I understand... Error is triggered by test
>/usr/src/netbsd-9/src/external/bsd/iscsi/lib/../dist/src/lib/disk.c line
>1405 when initiator sends data greater than 1MB.
>Why this limitation ?
Apparently to avoid allocating an arbitrary sized
Le 21/02/2020 à 10:57, BERTRAND Joël a écrit :
Maxime Villard a écrit :
Hi,
1) How much ram does your system have?
16 GB
2) If you add "#define NO_X86_ASLR" at the top of
sys/arch/x86/x86/pmap.c, does
the system boot fine?
I cannot try. Maybe the next week.
If I understand... Error is triggered by test
/usr/src/netbsd-9/src/external/bsd/iscsi/lib/../dist/src/lib/disk.c line
1405 when initiator sends data greater than 1MB.
Why this limitation ?
JKB
Hello,
My swap over iSCSI runs slowly. Very slowly. I have checked server log
and I have found :
Feb 21 18:20:12 legendre iscsi-target: > iSCSI Normal login successful
from iqn.1993-08.org.debian:01:f44d59dfc4a1 on 192.168.10.103 disk 0,
ISID 9613344773, TSIH 4359
Feb 21 18:20:12
Hi, is it advisable to NOT enable log option for FFSv2 that resides on
SD card due to flash memory wearing out in those regions, or does it
make no practical difference because of built-in wear levelling?
On Fri, 21 Feb 2020 13:40:03 +
David Brownlee wrote:
> On Fri, 21 Feb 2020 at 10:45, Sad Clouds
> wrote:
> >
> > Hi, anyone knows the current status of ZFS for recently released
> > NetBSD-9? There is a message on the console - "WARNING: ZFS on
> > NetBSD is under development". OK, but what
Chavdar Ivanov writes:
[snip]
>> > You export raw partition device; if you want to have many targets from
>> > one physical disk, you split the disk in any way you can - fdisk,
>> > gpt/dkctl or ZFS zvols and export the raw varieties of those.
>>
>> I have tried to export /dev/rwd0e to
Todd mailed me photos off list, the error is:
nouveau0: error: unknown chipset (16800a1)
and later it fails (kernel page fault) in nvkm_vdevice_*
Martin
On Fri, 21 Feb 2020 at 10:45, Sad Clouds wrote:
>
> Hi, anyone knows the current status of ZFS for recently released
> NetBSD-9? There is a message on the console - "WARNING: ZFS on NetBSD
> is under development". OK, but what does this mean? There is a good
> chance it may lose/corrupt data, or
On Fri, 21 Feb 2020 at 13:20, BERTRAND Joël wrote:
>
> Chavdar Ivanov a écrit :
> > On Fri, 21 Feb 2020 at 12:41, BERTRAND Joël
> > wrote:
> >>
> >> With
> >>
> >> # extentfile or device start length
> >> extent0 /dev/rwd0 0 32GB
> >>
> >> # target
Chavdar Ivanov a écrit :
> On Fri, 21 Feb 2020 at 12:41, BERTRAND Joël wrote:
>>
>> With
>>
>> # extentfile or device start length
>> extent0 /dev/rwd0 0 32GB
>>
>> # targetflags storage netmask
>> target0 rw extent0 192.168.10.103/32
On Fri, 21 Feb 2020 at 12:41, BERTRAND Joël wrote:
>
> With
>
> # extentfile or device start length
> extent0 /dev/rwd0 0 32GB
>
> # targetflags storage netmask
> target0 rw extent0 192.168.10.103/32
>
> iscsid seems to run as
On Fri, Feb 21, 2020 at 07:13:03AM -0500, Todd Gruhn wrote:
> At the end of the boot sequence, it drops me into the
> kernel debugger.
Give us a hint, what does it say?
I would expect something like:
panic:
followed by a stack backtrace that might be longish. If in doubt, take
a photo of
I have a new box with a Gigabyte Z390 Gaming X motherboard.
I comes with UEFI and UEFI-compatibility support module.
At the end of the boot sequence, it drops me into the
kernel debugger.
This is an initial install -- I am currently running the latest version of
Windoze. Any help would be
With
# extentfile or device start length
extent0 /dev/rwd0 0 32GB
# targetflags storage netmask
target0 rw extent0 192.168.10.103/32
iscsid seems to run as expected. But if I want to export a second
target, how can I modify targets
Hello,
I'm trying to configure a iSCSI target on a NetBSD 9.0. I have added a
new disk in my NIS/NFS server that appears as /dev/rwd0.
legendre# fdisk /dev/wd0
Disk: /dev/wd0d
NetBSD disklabel disk geometry:
cylinders: 310101, heads: 16, sectors/track: 63 (1008 sectors/cylinder)
Hi, anyone knows the current status of ZFS for recently released
NetBSD-9? There is a message on the console - "WARNING: ZFS on NetBSD
is under development". OK, but what does this mean? There is a good
chance it may lose/corrupt data, or it's pretty stable but watch out
for minor issues?
Maxime Villard a écrit :
> Hi,
>
> 1) How much ram does your system have?
16 GB
> 2) If you add "#define NO_X86_ASLR" at the top of
> sys/arch/x86/x86/pmap.c, does
> the system boot fine?
I cannot try. Maybe the next week.
I have tried to reboot this server and I
On 21/02/2020 03:38, Julien Savard wrote:
Hi,
it seems that since my last fedora upgrade ( 30 -> 31 ) I cannot boot any
NetBSD Guest running on KVM-Qemu.
Actual version on Fedora 31 is qemu-kvm-4.1.1-1.
NetBSD 8.0/8.1 On HD hang on : "NetBSD/x86 ffsv2 Primary Bootstrap"
NetBSD 9.0 booting on
25 matches
Mail list logo
