Date: Tue, 24 Feb 2015 11:21:23 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 197989] gpart(8) can't define start for new partition Message-ID: <bug-197989-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197989 Bug ID: 197989 Summary: gpart(8) can't define start for new partition Product: Base System Version: 11.0-CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: timp87@gmail.com Hi! There is a problem with gpart(8) in some cases. I have HP Proliant server with smart array raid controller (ciss driver). Sometimes gpart(8) can't define the start of a new partition that I want to add. Here is an example: Two disks build into one mirror using HP Smart Array. # gpart create -s gpt da0 da0 created # gpart add -t freebsd-ufs -s 512k da0 ad0p1 added # gpart show => 40 286677040 da0 GPT (137G) 40 752 - free - (376K) 792 1024 1 freebsd-ufs (512K) 1816 286675264 - free - (137G) # gpart add -t freebsd-ufs -s 512k da0 gpart: start '792': No space left on device What? But I have free space on device. And why gpart(8) tries to add new partition from 792? I already have such partition. It should start from 1816! Same story with MBR scheme, with 10.1-STABLE and 10.1-RELEASE. Looks like gpart(8) is buggy. FreeBSD 11.0-CURRENT amd64 r279210 (from 2015-02-23) -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-197989-8>