headers
Marin Atanasov | 1 Oct 2009 01:05
Picon
Gravatar

gmirror issue?

Hi,

I was doing some tests under 8.0-RC1 and noticed that when I set-up a 
root partition with gmirror, after the first reboot with the new 
mirrored root partition the system is not able to continue the boot process.

The error message that is being printed is this:

pid 63 (swapon), uid 0: exited on signal 11
....
pid 65: (fsck), uid 0: exited on signal 11
Segmentation fault
Unknown error; help!
ERROR: ABORTING BOOT (sending SIGTERM to parent)!

The full details about the implementation setup I'm using with 
gmirror/gvinum are described here:
http://www.daemonforums.org/showthread.php?p=27010#post27010

Regards,
Marin
Permalink | Reply | 2 comments |
headers
Marin Atanasov | 1 Oct 2009 08:27
Picon
Gravatar

Re: gmirror issue?

Marin Atanasov wrote:
> Hi,
>
> I was doing some tests under 8.0-RC1 and noticed that when I set-up a 
> root partition with gmirror, after the first reboot with the new 
> mirrored root partition the system is not able to continue the boot 
> process.
>
> The error message that is being printed is this:
>
> pid 63 (swapon), uid 0: exited on signal 11
> ....
> pid 65: (fsck), uid 0: exited on signal 11
> Segmentation fault
> Unknown error; help!
> ERROR: ABORTING BOOT (sending SIGTERM to parent)!
>
>
> The full details about the implementation setup I'm using with 
> gmirror/gvinum are described here:
> http://www.daemonforums.org/showthread.php?p=27010#post27010
>
> Regards,
> Marin
>
Forgot to mention that this error only occurs the first time you boot 
into your 8.0-RC1 system, after when you have set-up root with the new 
mirror filesystem. This does not apply for 7.2

Also the real issue for this is that /etc/fstab contains one new line at
(Continue reading)

Permalink | Reply | 1 comment |
headers
Frank Beckmann | 3 Oct 2009 15:43
Picon
Favicon

Virstor provider lost metadata. Rescue possible?

Hello,

one of my virstor providers lost its metadata. It looks like the sector got filled with random data. it is the
second last filled sector in that virstor. Executing the command "gvirstor list", "gvirstor status" or
"sysctl -a" resulted in a kernel panic.

I handcrafted the destroyed sector assuming that all chunks of that provider were used and setting the
flags to 0. Now the kernel doesn't panic anymore but I get the error message:

GEOM_VIRSTOR[1]: virstor_check_and_run: Invalid entry 100542 in map for vs3
GEOM_VIRSTOR[1]: virstor_check_and_run: provider_no: 25, n_components: 33 provider_chunk: 512,
chunk_count 512

Provider 25 is the one which lost its metadata.

The version of FreeBSD is: 7.2-RC1

Is it possible to revive that virstor to rescue some of its data?

Thanks for any help.
Frank
Permalink | Reply | 1 comment |
headers
FreeBSD bugmaster | 5 Oct 2009 13:06
Picon
Favicon

Current problem reports assigned to freebsd-geom <at> FreeBSD.org

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/135898  geom       [geom] Severe filesystem corruption - large files or l
o kern/134922  geom       [gmirror] [panic] kernel panic when use fdisk on disk 
o kern/134113  geom       [geli] Problem setting secondary GELI key
o kern/134044  geom       [geom] gmirror(8) overwrites fs with stale data from r
o kern/133931  geom       [geli] [request] intentionally wrong password to destr
o bin/132845   geom       [geom] [patch] ggated(8) does not close files opened a
o kern/132273  geom       glabel(8): [patch] failing on journaled partition
f kern/132242  geom       [gmirror] gmirror.ko fails to fully initialize
o kern/131353  geom       [geom] gjournal(8) kernel lock
p docs/130548  geom       [patch] gjournal(8) man page is missing sysctls
o kern/129674  geom       [geom] gjournal root did not mount on boot
o kern/129645  geom       gjournal(8): GEOM_JOURNAL causes system to fail to boo
o kern/129245  geom       [geom] gcache is more suitable for suffix based provid
f kern/128276  geom       [gmirror] machine lock up when gmirror module is used
f kern/126902  geom       [geom] geom_label: kernel panic during install boot
o kern/124973  geom       [gjournal] [patch] boot order affects geom_journal con
o kern/124969  geom       gvinum(8): gvinum raid5 plex does not detect missing s
f kern/124294  geom       [geom] gmirror(8) have inappropriate logic when workin
o kern/123962  geom       [panic] [gjournal] gjournal (455Gb data, 8Gb journal),
o kern/123122  geom       [geom] GEOM / gjournal kernel lock
o kern/122738  geom       [geom] gmirror list "losts consumers" after gmirror de
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sean C. Farley | 5 Oct 2009 17:37
Picon
Favicon

Re: gmirror issue?

On Thu, 1 Oct 2009, Marin Atanasov wrote:

> Marin Atanasov wrote:
>> Hi,
>> 
>> I was doing some tests under 8.0-RC1 and noticed that when I set-up a 
>> root partition with gmirror, after the first reboot with the new 
>> mirrored root partition the system is not able to continue the boot 
>> process.
>> 
> Forgot to mention that this error only occurs the first time you boot 
> into your 8.0-RC1 system, after when you have set-up root with the new 
> mirror filesystem. This does not apply for 7.2
>
> Also the real issue for this is that /etc/fstab contains one new line 
> at the end of the file like this:
> ^ <at> ^ <at> ^ <at> ^ <at> 

While I cannot help with the other issues, I wanted to state I have seen 
this too.  I see these characters when installing via a serial 
connection (using VirtualBox).  They appear after every line I paste 
into the telnet connection (mode character).

Are you doing something similar?

Sean
--

-- 
scf <at> FreeBSD.org
Permalink | Reply | 0 comments |
headers
Azim | 6 Oct 2009 13:21
Favicon

Re: Issue with Device file /dev/ad4s5


Solved. I deleted the D DRIVE PARTITION completely. Now I again had free
space. I Recreated the same partition with the same amount of size and
now I do see /dev/ad4s5. Thanks.
-- 
  Azim

--

-- 
http://www.fastmail.fm - Email service worth paying for. Try it for free
Permalink | Reply | 0 comments |
headers
Ivan Voras | 12 Oct 2009 09:44
Picon
Favicon
Gravatar

Re: Virstor provider lost metadata. Rescue possible?

Frank Beckmann wrote:
> Hello,
> 
> one of my virstor providers lost its metadata. It looks like the sector got filled with random data. it is
the second last filled sector in that virstor. Executing the command "gvirstor list", "gvirstor status"
or "sysctl -a" resulted in a kernel panic.
> 
> I handcrafted the destroyed sector assuming that all chunks of that provider were used and setting the
flags to 0. Now the kernel doesn't panic anymore but I get the error message:
> 
> GEOM_VIRSTOR[1]: virstor_check_and_run: Invalid entry 100542 in map for vs3
> GEOM_VIRSTOR[1]: virstor_check_and_run: provider_no: 25, n_components: 33 provider_chunk: 512,
chunk_count 512
> 
> Provider 25 is the one which lost its metadata.
> 
> The version of FreeBSD is: 7.2-RC1
> 
> Is it possible to revive that virstor to rescue some of its data?

This is a serious problem, but as long as the first component of the
virstor is alive and, as you say, only the metadata is damaged on
component 25 (of 33), there is a chance.

It looks like chunk_count is wrong for provider 25 - it holds the number
of chunks (of default 4 MiB) on the device. You could calculate
device_size/4194304 and write it in the chunk_count field of the
reconstructed metadata - see if that helps (reference
/sys/geom/virstor/g_virstor_md.h).
(Continue reading)

Permalink | Reply | 0 comments |
headers
FreeBSD bugmaster | 12 Oct 2009 13:06
Picon
Favicon

Current problem reports assigned to freebsd-geom <at> FreeBSD.org

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/135898  geom       [geom] Severe filesystem corruption - large files or l
o kern/134922  geom       [gmirror] [panic] kernel panic when use fdisk on disk 
o kern/134113  geom       [geli] Problem setting secondary GELI key
o kern/134044  geom       [geom] gmirror(8) overwrites fs with stale data from r
o kern/133931  geom       [geli] [request] intentionally wrong password to destr
o bin/132845   geom       [geom] [patch] ggated(8) does not close files opened a
o kern/132273  geom       glabel(8): [patch] failing on journaled partition
f kern/132242  geom       [gmirror] gmirror.ko fails to fully initialize
o kern/131353  geom       [geom] gjournal(8) kernel lock
p docs/130548  geom       [patch] gjournal(8) man page is missing sysctls
o kern/129674  geom       [geom] gjournal root did not mount on boot
o kern/129645  geom       gjournal(8): GEOM_JOURNAL causes system to fail to boo
o kern/129245  geom       [geom] gcache is more suitable for suffix based provid
f kern/128276  geom       [gmirror] machine lock up when gmirror module is used
f kern/126902  geom       [geom] geom_label: kernel panic during install boot
o kern/124973  geom       [gjournal] [patch] boot order affects geom_journal con
o kern/124969  geom       gvinum(8): gvinum raid5 plex does not detect missing s
f kern/124294  geom       [geom] gmirror(8) have inappropriate logic when workin
o kern/123962  geom       [panic] [gjournal] gjournal (455Gb data, 8Gb journal),
o kern/123122  geom       [geom] GEOM / gjournal kernel lock
o kern/122738  geom       [geom] gmirror list "losts consumers" after gmirror de
(Continue reading)

Permalink | Reply | 0 comments |
headers
pjd | 13 Oct 2009 07:48
Picon
Favicon

Re: kern/139510: [geom] [2tb] gmirror disappears after boot on 2T disks

Synopsis: [geom] [2tb] gmirror disappears after boot on 2T disks

State-Changed-From-To: open->feedback
State-Changed-By: pjd
State-Changed-When: wto 13 pa¼ 2009 05:44:07 UTC
State-Changed-Why: 
Please add kern.geom.mirrror.debug=2 to your /boot/loader.conf and send
the additional output from the boot process.

I'd also need the following:

	# gmirror dump /dev/ad1[48]
	# diskinfo -v /dev/ad1[48]

Responsible-Changed-From-To: freebsd-geom-≥pjd
Responsible-Changed-By: pjd
Responsible-Changed-When: wto 13 pa¼ 2009 05:44:07 UTC
Responsible-Changed-Why: 
I'll take this one.

http://www.freebsd.org/cgi/query-pr.cgi?pr=139510
Permalink | Reply | 1 comment |
headers
Michal | 15 Oct 2009 23:45
Picon

how does geli interact with ZFS?

Hello,

I'm using root ZFS on geli encrypted partition (with /boot on UFS usb 
dongle). Does adding this extra layer between ZFS and disk can get me 
into troubles in case of a system crash?
I mean, does it affects zfs's robustness and features like 
Copy-On-Write, checksumming or anything else? Or it can only get as bad 
as with plain ZFS and geom_eli has nothing to do with that.

Michal
--

-- 
"It is only when they go wrong that machines remind you how powerful 
they are." -Clive James
Permalink | Reply | 2 comments |

Gmane