Zlog benchmark with diskinfo, Flush error: operation not supported

2017-10-10 Thread Olav Gjerde 
Hello, I just tried to run the recently added slog benchmark for
diskinfo on 11.1-Release. It works fine with ATA drives, but not with
NVMe drives. I get the following error

# diskinfo -vSw /dev/nvd0
/dev/nvd0
512 # sectorsize
400088457216# mediasize in bytes (373G)
781422768   # mediasize in sectors
131072  # stripesize
0   # stripeoffset
CVFT4291009H400GGN# Disk ident.

Synchronous random writes:
 0.5 kbytes: diskinfo: Flush error: Operation not supported


kern.geom.debugflags is of course set to 16, these drives does not
have any partitions either.
They also do not show up with camcontrol devlist.

What do work though, is creating a partition, ufs file system and
dummy file which I can then run this benchmark on.

Is this a configuration issue or a bug?

-- 
Kind Regards / Med Vennlig Hilsen

Olav Grønås Gjerde

BackupBay Gjerde
Asalvegen 19
4051 SOLA
Norway
Phone: +47 918 000 59
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dd: vm_fault: pager read error

2017-10-10 Thread grarpamp 
> Eugene Grosbein  wrote:
>> Was there a ticket and revision number to look into that?
>> Because this issue is still present in 11.1 and r324300.

> It was meant to be
> https://svnweb.freebsd.org/base?view=revision=date=320566

Found the thread... seems the same "Device not configured" problem,
just triggered differently by different users...
https://lists.freebsd.org/pipermail/freebsd-stable/2017-June/thread.html

I think 320566 may have quashed the two pager messages bits
(I don't seem to get them anymore), but the "Device not configured"
issue people observed is still there.

> If you are sure running kernel after 320566

Both 11.1R (r321309) and r324300 (same as snapshot) are after that.

> you should fill a PR.

Assuming there's not already one.
Then one for this issue when cleaned up.
And probably another for the geom.debugflags footshooting semantics.

Also I need to capture that mount -uw panic but have to look up again
the sysctl to prevent instant reboot / leave it onscreen or to debugger.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: console-only freebsd

2017-10-10 Thread tech-lists 

On Mon, Oct 09, 2017 at 07:58:12AM -0700, Chris H wrote:


You might also find this article by Warren Block of value:

http://www.wonkity.com/~wblock/docs/html/hiresconsole.html


interesting, I guess that's another way of looking at it. Bear in mind 
though that the cpu really is low powered. On top of that, it's a netbook so
keeping power consumption low is important 


In the meantime I've found that links2 might do what I want as it supports
text and graphics in svga/framebuffer.

thanks for the suggestion

--
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: automount usb msdosfs no partition table

2017-10-10 Thread Tomoaki AOKI 
Does sysutils/automount (not sysutils/automounter) work as expected?

 *Need fix for head, though. The fix itself is easy, but I've stuck
  with version check to create extra patch for ports.

Attached patch for head. If you want to use sysutils/automount on head,
apply it as root AFTER install for now.


On Mon, 9 Oct 2017 21:07:29 +0200
Tomasz CEDRO  wrote:

> On Mon, Oct 9, 2017 at 8:59 PM, Scott Bennett  wrote:
> > Tomasz CEDRO  wrote:
> >> i cannot format that device, as its the "firmware feature" that it has no
> >> partition table.. i would have to fix the firmware.. but it would be nice
> >> to automount it anyway as macos, linux and windoze can :-)
> >  Well, put a partition table onto it, then.  You can use either gpart(8)
> > or fdisk(8) to do that and to create a slice, and then use newfs_msdos(8) to
> > create the file system.
> >  I understood from your previous message that you wanted to create a 
> > FAT32
> > file system on /dev/da0 rather than on /dev/da0s1, which meant on the bare
> > device rather than on a slice.  Otherwise, create the partition table, 
> > create
> > a slice, and proceed.
> 
> The problem is device has hardcoded filesystem, with no partition
> table, all this is created by firmware on device boot, cannot get
> formatted nor partitioned.. I can mount it by hand.. but it does not
> get automounted.. and exactly this part is the problem and quest here
> :-) :-)
> 
> -- 
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
> 


-- 
Tomoaki AOKI
--- /usr/local/sbin/automount.orig	2015-09-21 16:10:07.114602000 +0900
+++ /usr/local/sbin/automount	2017-09-30 00:23:51.855577000 +0900
@@ -423,12 +423,12 @@ case ${2} in
   __log "${DEV}: fsck_msdosfs ${LINE}"
 done
 __wait_for_device ${DEV}
-if mount_msdosfs ${OPTS} -o large -o longnames -m 644 -M 755 \
+if mount_msdosfs ${OPTS} -o longnames -m 644 -M 755 \
  -D ${CODEPAGE} -L ${ENCODING} ${DEV} ${MNT}
 then
   ADD=1
 else
-  __log "${DEV}: mount failed (fat) 'mount_msdosfs ${OPTS} -o large -o longnames -D ${CODEPAGE} -L ${ENCODING} -m 644 -M 755 ${DEV} ${MNT}'"
+  __log "${DEV}: mount failed (fat) 'mount_msdosfs ${OPTS} -o longnames -D ${CODEPAGE} -L ${ENCODING} -m 644 -M 755 ${DEV} ${MNT}'"
   exit 1
 fi
 __log "${DEV}: mount (fat)"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: console-only freebsd

2017-10-10 Thread Jakub Lach 
Exactly, I would still use X, just with a frugal wm (dwm).



--
Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-stable-f3932046.html
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dd: vm_fault: pager read error

2017-10-10 Thread Eugene Grosbein 
10.10.2017 15:06, grarpamp пишет:
> On Sun, Oct 8, 2017 at 3:05 PM, Eugene Grosbein  wrote:
>> The problem is known and already fixed. You should upgrade.
> 
> Was there a ticket and revision number to look into that?
> Because this issue is still present in 11.1 and r324300.

It was meant to be 
https://svnweb.freebsd.org/base?view=revision=date=320566
If you are sure running kernel after 320566, you should fill a PR.

Please be more specific of your configuration, including full 'gpart show' 
output,
list of mounted file systems, uname -K output, exact text of commands and 
system responces.


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: dd: vm_fault: pager read error

2017-10-10 Thread grarpamp 
On Sun, Oct 8, 2017 at 3:05 PM, Eugene Grosbein  wrote:
> The problem is known and already fixed. You should upgrade.

Was there a ticket and revision number to look into that?
Because this issue is still present in 11.1 and r324300.

When booting either from usb...

- Mounting ada0s1a read-only on /mnt, and giving the same
dd, still produces "Device not configured" upon an ls -R /mnt.
A umount clears that condition. Repeat.

- After triggering it read-only, but not unmounting to clear
it, a mount -uw panics the box.

- Giving the dd in unmounted state appears to be ok.


Another issue:

debugflags=16, manpage say 'allow[s]...write[ing]...sectors... to
mounted [read-write?] disk [the aforesaid mounted partition on it?]".
The manpage is unclear there. Also geom(8) does not display
that actual rank status info, ie: "Rank 1 provider". IMO, 16 should
"allow [all] foot shooting".
So mode 16 appears to be broken because the dd is denied,
even though the dd is NOT writing to the read-write mounted
s1a partition itself (which should be allowed even if it were),
but is seeking over past it.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"