Re: aliasing (or renaming) kern.geom.debugflags

In message <alpine.BSF.2.00.1110071352210.2450@wonkity.com>, Warren Block write
s:

># mount /dev/da0p2 /mnt
># dd if=/tmp/FreeBSD-9.0-BETA3-amd64-memstick.img of=/dev/da0 bs=64k
>dd: /dev/da0: Operation not permitted
># sysctl kern.geom.debugflags=16
>kern.geom.debugflags: 0 -> 16
># dd if=/tmp/FreeBSD-9.0-BETA3-amd64-memstick.img of=/dev/da0 bs=64k
>10463+1 records in
>10463+1 records out
>685731840 bytes transferred in 52.915362 secs (12959031 bytes/sec)
>
>Followed by removing the memory stick without unmounting it to avoid 
>overwriting part of the image.  No obvious problems, but no, it's not 
>polite.  (I'm thinking "automounter" here.)

And you are sure the stick now contains what you expect ?

If the dirty filesystem had blocks to write, it might have done so...

debugflags are called debugflags for a reason:  You should never
need them, unless you are debugging a problem.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"