Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Philip Guenther
On Sat, May 28, 2016 at 9:15 AM, Robert Campbell wrote: >... > # bioctl -c C -l sd0a softraid0 > New passphrase: > Re-type passphrase: > sd3 at scsibus3 targ 1 lun 0: SCSI2 0/direct fixed > sd3: 114470MB, 512 bytes/sector, 234435953 sectors > softraid0: CRYPTO volume attached as sd3 > # dd if=/de

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Ivan Markin
Stefan Sperling: > On Sat, May 28, 2016 at 06:03:48PM +, Ivan Markin wrote: >> Sebastien Marie: >>> Do you run these commands on the ramdisk (bsd.rd) ? If yes, all the >>> /dev/sd* aren't created by default. >> >> Why it is so? Can this be found somewhere in documentation? > > If the ramdisk s

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Ivan Markin
Sebastien Marie: > Do you run these commands on the ramdisk (bsd.rd) ? If yes, all the > /dev/sd* aren't created by default. Why it is so? Can this be found somewhere in documentation? -- Ivan Markin

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Theo Buehler
On Sat, May 28, 2016 at 08:03:47PM +0200, Stefan Sperling wrote: > On Sat, May 28, 2016 at 06:15:35PM +0200, Robert Campbell wrote: > > I followed the steps in the FAQ for setting up full disk encryption. > > Everything goes according to plan until I attempt to write zeros to the > > first megabyte

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Stefan Sperling
On Sat, May 28, 2016 at 06:15:35PM +0200, Robert Campbell wrote: > I followed the steps in the FAQ for setting up full disk encryption. > Everything goes according to plan until I attempt to write zeros to the > first megabyte of the new pseudo-device; as you can see below, dd informs > me that the

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Theo de Raadt
> On Sat, May 28, 2016 at 06:15:35PM +0200, Robert Campbell wrote: > > I followed the steps in the FAQ for setting up full disk encryption. > > Everything goes according to plan until I attempt to write zeros to the > > first megabyte of the new pseudo-device; as you can see below, dd informs > > m

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Stefan Sperling
On Sat, May 28, 2016 at 06:03:48PM +, Ivan Markin wrote: > Sebastien Marie: > > Do you run these commands on the ramdisk (bsd.rd) ? If yes, all the > > /dev/sd* aren't created by default. > > Why it is so? Can this be found somewhere in documentation? If the ramdisk shipped with all possible

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Sebastien Marie
On Sat, May 28, 2016 at 06:15:35PM +0200, Robert Campbell wrote: [...] > # dd if=/dev/zero of=/dev/rsd3c bs=1m count=1 > uid 0 on /: file system full > > /: write failed, file system is full > dd: /dev/rsd3c: No space left on device > 1+0 records in > 0+0 records out > 0 bytes transferred in 0.00

Re: CRYPTO volume created, but appears as full

2016-05-28 Thread Ivan Markin
Robert Campbell: > I followed the steps in the FAQ for setting up full disk encryption. > Everything goes according to plan until I attempt to write zeros to the > first megabyte of the new pseudo-device; as you can see below, dd informs > me that the file system is full, that there is no space lef

CRYPTO volume created, but appears as full

2016-05-28 Thread Robert Campbell
I followed the steps in the FAQ for setting up full disk encryption. Everything goes according to plan until I attempt to write zeros to the first megabyte of the new pseudo-device; as you can see below, dd informs me that the file system is full, that there is no space left on the device. Interest