Bug 131037 - [geli] Unable to create disklabel on .eli-Device
Summary: [geli] Unable to create disklabel on .eli-Device
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-geom (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-27 11:00 UTC by Hannes Hauswedell
Modified: 2009-08-11 14:34 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hannes Hauswedell 2009-01-27 11:00:12 UTC
I am having serious problems creating a label on a geli'ed slice.

I have posted this on freebsd-geom, but havent gotten any repsonses so far. It is quite urgent for me to get this running though and it does look like a bug, so I posted here.

I can create the slice, create the geli container and write a standard label to it. As soon as I edit the label and save it (even if not changing anything from the default) I get:

WARNING: Expected rawoffset 487974, found 487974

(Or another number depending on where I created the slice...)


Which looks strange in itself - after all, what kind of messages does GEOM give if does NOT find the expected offset? ^^


I tried to ignore the warning and just started copying data on a 
partition inside the slice, but got a reboot with geli-write errors (=5)
in /var/log/messages.

I tried repartitioning and relabeling multiple times to no avail.

Thanks for any help!

Hannes


P.S: ar0 is a soft-raid of 1TB Samsung F1 EcoGreen and 1TB WD Cavier Green EADS. The errors also occur when working on each disk individually.

Fix: 

I tried to read the part in sys/geom/geom_bsd.c that produces the warning, but don't understand it :(
Then again it is prefixed by:
/* Historical braindamage... */ 

So I don't know if anyone else does :/
How-To-Repeat: geli init -l 256 -K MYKEY -s 4096 /dev/ar0s2
geli attach -k MYKEY /dev/ar0s2
bsdlabel -w /dev/ar0s2.eli
bsdlabel -e /dev/ar0s2.eli
(change nothing and exit EDITOR)
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-01-27 15:55:00 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-geom

Over to maintainer(s).
Comment 2 Hannes Hauswedell 2009-01-29 15:06:44 UTC
The panic seems not to be connected to the warning.

I partitioned the .eli with gpt and received no warnings, but still got 
a reboot while writing. I changed some options on the raid-adapter 
(which isn't supported by freebsd anyway - the raid is softraid) and 
now I don't have any panics.

So GPT works fine for me and I will be using that. I can't verify 
whether it would have worked with bsdlabels as well but I think so.

The warning in itself should still be considered a bug, but not really 
important. You may change or close this PR, however you see fit.

In case someone wants to work on the warning, here are the infos that 
may help:

Warning appears if you have 
UFS <-> bsd-partition <-> bsdlabel <-> .eli <-> freebsd-slice 
-> /dev/ad0s1.elia

Warning DOES NOT appear if you have:
UFS <-> .eli <-> freebsd-slice
->/dev/ad0s1.eli

OR: UFS <-> bsd-partition <-> bsdlabel <-> .eli
-> /dev/ad0.elia

OR: UFS <-> gpt-partition <-> gpt-layout <-> .eli <-> freebsd-slice 
-> /dev/ad0s1.elip1

OR: UFS <-> bsd-partition <-> bsdlabel <-> freebsd-slice 
-> /dev/ad0s1a


Regards,
Hannes
Comment 3 Pawel Jakub Dawidek freebsd_committer freebsd_triage 2014-06-01 06:59:58 UTC
State Changed
From-To: open->closed

Closing at submitter's request. Not a geli problem anyway.