On Mon, Mar 21, 2011 at 12:30 AM, Carl Johnson ca...@peak.org wrote:
Maxim Khitrov m...@mxcrypt.com writes:
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote:
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match
On Mon, 21 Mar 2011 06:40:51 -0400, Maxim Khitrov m...@mxcrypt.com wrote:
I've been using 'dangerously dedicated' partitioning for years without
any issues. What problems have been reported by others?
I think those problems originate from some operating systems
not able to work with disks that
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match label kernel messages (FreeBSD 8.2
amd64). I understand why they happen - glabel metadata occupies the
last sector, so bsdlabel sees a device that is 1 sector smaller than
what the kernel
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote:
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match label kernel messages (FreeBSD 8.2
amd64). I understand why they happen - glabel metadata occupies the
last
Maxim Khitrov m...@mxcrypt.com writes:
On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov m...@mxcrypt.com wrote:
Hi all,
Executing the following commands on any valid storage device seems to
cause media size does not match label kernel messages (FreeBSD 8.2
amd64). I understand why they happen
