headers
FreeBSD bugmaster | 3 Jan 2011 12:07
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/152609  geom       [geli] geli onetime on gzero panics
o kern/150858  geom       [geom] [geom_label] [patch] glabel(8) is not compatibl
o kern/150626  geom       [geom] [gjournal] gjournal(8) destroys label
o kern/150555  geom       [geom] gjournal unusable on GPT partitions
o kern/150334  geom       [geom] [udf] [patch] geom label does not support UDF
o kern/149762  geom       volume labels with rogue characters
o bin/149215   geom       [panic] [geom_part] gpart(8): Delete linux's slice via
o kern/147852  geom       [geom] [panic] graid3 panic: wrong offset 16384 for se
o kern/147851  geom       [geom] [panic] graid3 panic: g_read_data: invalid leng
o kern/147667  geom       [gmirror] Booting with one component of a gmirror, the
o kern/147664  geom       [geom] [patch] Add the ability to create linux and fat
o kern/145818  geom       [geom] geom_stat_open showing cached information for n
o kern/145042  geom       [geom] System stops booting after printing message "GE
o kern/144962  geom       [geom] panic when accessing GPT disk with a large numb
o kern/144905  geom       [geom][geom_part] panic in gpart_ctlreq when unpluggin
o kern/143455  geom       gstripe(8) in RELENG_8 (31st Jan 2010) broken
o kern/142563  geom       [geom] [hang] ioctl freeze in zpool
o kern/141740  geom       [geom] gjournal(8): g_journal_destroy concurrent error
o kern/140352  geom       [geom] gjournal + glabel not working
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
(Continue reading)

Permalink | Reply | 0 comments |
headers
Zeus V Panchenko | 4 Jan 2011 18:06
Picon
Gravatar

"secondary GPT table is corrupt or invalid" issue again

Hi,

i was unable to find clear answer and decided to ask here

the subj was asked several times but no answer i can use to get rid of
the message ... please, advice if possible what to do?

> uname -a
FreeBSD 8.1-RELEASE amd64

ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <WDC WD5000AAKS-00YGA0 12.01C02> ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 476940MB (976773168 512 byte sectors: 16H 63S/T 16383C)
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <WDC WD10EARS-00Y5B1 80.00A80> ATA-8 SATA 2.x device
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <WDC WD10EARS-00Y5B1 80.00A80> ATA-8 SATA 2.x device
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)

ada0 is system disk

ada1 and ada2 are gparted as GPT and gmirrored for the storage ...
(Continue reading)

Permalink | Reply | 12 comments |
headers
Lev Serebryakov | 7 Jan 2011 18:28
Picon
Favicon

Re: Building "third-party" modules for kernel with debug options?

Hello, John.
You wrote 7 января 2011 г., 16:20:23:

>>   I've found, that "struct bio" is depend on state of "DIAGNOSTIC"
>> flag ("options DIAGNOSTIC" in kernel config). But when I build
>> third-party GEOM (or any other) module with using of <bsd.kmod.mk>,
>> there is no access to these options. So, module, built from ports, can
>> fail on user's kernel, even if it built with proper kernel sources in
>> "/usr/src/sys". Is here any solution for this problem?
>> 
>> P.S. NB: GEOM module is only example, question is about modules &
>> kernel options in general, so I put this message on Hackers list.

> In general we try to avoid having "public" kernel data structures change size
> when various kernel options are in use.  Some noticeable exceptions to this
> rule are PAE (i386-only) and LOCK_PROFILING (considered to be something users
> would not typically use).  DIAGNOSTIC might arguably be considered the same as
> LOCK_PROFILING, but I am surprised it affects bio.  It should only affect a
> GEOM module that uses bio_pblockno however in this case since you should be
> using kernel routines to allocate bio structures rather than malloc'ing one
> directly.  Perhaps phk <at>  would ok moving bio_pblockno up above the optional
> diagnostic fields.
  I've  got  "bio_caller2 used by the provider XXX" panic when kernel
  had DIAGNOSTIC and goem_raid5 had not...

  I've   redirected  this  answer  into  GEOM  list,  as  it  is  more
  GEOM-specific than my original message.

--

-- 
// Black Lion AKA Lev Serebryakov <lev <at> FreeBSD.org>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrey V. Elsukov | 8 Jan 2011 12:55
Picon
Favicon

Re: "secondary GPT table is corrupt or invalid" issue again

On 04.01.2011 20:06, Zeus V Panchenko wrote:
> while booting, i have this:
> 
> GEOM: ada1: the secondary GPT table is corrupt or invalid.
> GEOM: ada1: using the primary only -- recovery suggested.
> GEOM: ada2: the secondary GPT table is corrupt or invalid.
> GEOM: ada2: using the primary only -- recovery suggested.
> GEOM_MIRROR: Device mirror/gm0 launched (2/2).
> 
> so, if it is because of gmirror data overwritten GPT than how to fix
> them?
> 
> if i need to reconfigure GPT or gmirror, than how and what, please?

FreeBSD 8.2 has implemented support of recovering GPT. You can try to
boot from livefs image or just update your system and use
'gpart recover'. But i strongly suggest to read related paragraph
in manual page before. Backup is recommended of course.

--

-- 
WBR, Andrey V. Elsukov
Permalink | Reply | 10 comments |
headers
Zeus V Panchenko | 8 Jan 2011 23:37
Picon
Gravatar

Re: "secondary GPT table is corrupt or invalid" issue again

Andrey V. Elsukov (bu7cher <at> yandex.ru) [11.01.08 13:55] wrote:
> 
> FreeBSD 8.2 has implemented support of recovering GPT. You can try to
> boot from livefs image or just update your system and use
> 'gpart recover'. But i strongly suggest to read related paragraph
> in manual page before. Backup is recommended of course.
> 

what if i detach one hdd from mirror, than recover the one in mirror
and attach the first one again, will it be right way?

--

-- 
Zeus V. Panchenko
IT Dpt., IBS ltd			      	        GMT+2 (EET)
Permalink | Reply | 9 comments |
headers
Luchesar V. ILIEV | 9 Jan 2011 01:02
Picon
Gravatar

Re: "secondary GPT table is corrupt or invalid" issue again

On 01/09/2011 00:37, Zeus V Panchenko wrote:
> Andrey V. Elsukov (bu7cher <at> yandex.ru) [11.01.08 13:55] wrote:
>>
>> FreeBSD 8.2 has implemented support of recovering GPT. You can try to
>> boot from livefs image or just update your system and use
>> 'gpart recover'. But i strongly suggest to read related paragraph
>> in manual page before. Backup is recommended of course.
>>
> 
> what if i detach one hdd from mirror, than recover the one in mirror
> and attach the first one again, will it be right way?
> 

Hi Zeus,

Just my two cents. If I understood correctly from your first mail,
you've set up the gmirror on /dev/ada{1,2}p1; that is, you're not
mirroring the whole disk, but just the (single) partition on it.

gmirror(8) stores its metadata in the last sector of the provider, and
since in your case that's the partition itself, I can't see how it could
have overwritten the secondary GPT. I was wondering if your problem
could be related to the ahci(4) driver? I think I've seen reports of
problems with data integrity; considering that this infrastructure is
not yet as mature as the old ata(4)-based one, this doesn't seem totally
impossible with certain devices. Then again, I'd find it a bit strange
to have only the secondary GPT get corrupt and nothing else if the
problem had indeed been in the ahci driver...

Speaking of that (and not related directly to your question), you might
(Continue reading)

Permalink | Reply | 8 comments |
headers
Zeus V Panchenko | 9 Jan 2011 10:27
Picon
Gravatar

Re: "secondary GPT table is corrupt or invalid" issue again

Hi Luchesar,

thank you for reply,
> 
> Just my two cents. If I understood correctly from your first mail,
> you've set up the gmirror on /dev/ada{1,2}p1; that is, you're not
> mirroring the whole disk, but just the (single) partition on it.
> 
really the history was this:
i configured first drive as GPT (whole dedicated drive), newfs-ed it
and filled with data

after what i created mirror on it but not on entire disk /dev/ada0 (not on it's
single partition /dev/ada0p1) and i believe it was the cause of corruption

latter i found maillist explanation of the mistake and reconfigured
the mirror to use partitions instead of entire disk ... so, this way
the corruption appeared as i can judge now 

> have overwritten the secondary GPT. I was wondering if your problem
> could be related to the ahci(4) driver? I think I've seen reports of

no, i do not believe it is ahci(4) related issue since no other
simpthomes were observed (smart data shows no problems too) 

> 
> # gmirror label -v -h -b load gm0 gpt/teradisk0
> # gmirror insert -v -h -p 1 gm0 gpt/teradisk1
> 
> Using -h is important here, as otherwise gmirror will "forget" the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Zeus V Panchenko | 9 Jan 2011 12:20
Picon
Gravatar

Re: "secondary GPT table is corrupt or invalid" issue again

and again ... just to be sure i understand all correctly ...  

now i have two disks in gmirror ... to get rid of the secondary table
corruption for my working gmirror (with mirror master ada1)

      Name    Status  Components
mirror/gm0  COMPLETE  ada1p1
                      ada2p1

i decided to destroy second (ada2) disk GPT and gmirror data, create
GPT for it (ada2) from scratch, copy data to it from gmirror (gm0),
destroy the mirror, create the mirror with second (ada2) disk as
master, recreate GPT for first (ada1) disk and insert it to the mirror
as secondary disk:

 1. gmirror remove gm0 ada2p1
 2. gmirror clear ada2p1
 3. gpart destroy ada2
 4. gpart create -s gpt /dev/ada2
 5. gpart add -b 2048 -s 1953521664 -t freebsd-ufs -i 1 -l labeldisk2 /dev/ada2
 6. newfs -f 4096 -b 32768 -g 1048576 -o space -U -L labeldisk2 /dev/ada2p1
 7. tar -cf - -C MNTPOIN_gm0 . | tar -xpf - -C MNTPOINT_ada2p1
 8. gmirror stop gm0 
 9. gpart destroy ada1
10. gpart create -s gpt /dev/ada1
11. gpart add -b 2048 -s 1953521664 -t freebsd-ufs -i 1 -l labeldisk1 /dev/ada1
12. newfs -f 4096 -b 32768 -g 1048576 -o space -U -L labeldisk1 /dev/ada1p1
13. gmirror label -v -h -b load gm0 gpt/labeldisk2
14. gmirror insert -v -h -p 1 gm0 gpt/labeldisk1
(Continue reading)

Permalink | Reply | 5 comments |
headers
Luchesar V. ILIEV | 9 Jan 2011 14:27
Picon
Gravatar

Re: "secondary GPT table is corrupt or invalid" issue again

On 01/09/2011 13:20, Zeus V Panchenko wrote:
> and again ... just to be sure i understand all correctly ...  
> 
> now i have two disks in gmirror ... to get rid of the secondary table
> corruption for my working gmirror (with mirror master ada1)
> 
>       Name    Status  Components
> mirror/gm0  COMPLETE  ada1p1
>                       ada2p1
> 
> i decided to destroy second (ada2) disk GPT and gmirror data, create
> GPT for it (ada2) from scratch, copy data to it from gmirror (gm0),
> destroy the mirror, create the mirror with second (ada2) disk as
> master, recreate GPT for first (ada1) disk and insert it to the mirror
> as secondary disk:
> 
>  1. gmirror remove gm0 ada2p1
>  2. gmirror clear ada2p1
>  3. gpart destroy ada2
>  4. gpart create -s gpt /dev/ada2
>  5. gpart add -b 2048 -s 1953521664 -t freebsd-ufs -i 1 -l labeldisk2 /dev/ada2
>  6. newfs -f 4096 -b 32768 -g 1048576 -o space -U -L labeldisk2 /dev/ada2p1
>  7. tar -cf - -C MNTPOIN_gm0 . | tar -xpf - -C MNTPOINT_ada2p1
>  8. gmirror stop gm0 
>  9. gpart destroy ada1
> 10. gpart create -s gpt /dev/ada1
> 11. gpart add -b 2048 -s 1953521664 -t freebsd-ufs -i 1 -l labeldisk1 /dev/ada1
> 12. newfs -f 4096 -b 32768 -g 1048576 -o space -U -L labeldisk1 /dev/ada1p1
> 13. gmirror label -v -h -b load gm0 gpt/labeldisk2
> 14. gmirror insert -v -h -p 1 gm0 gpt/labeldisk1
(Continue reading)

Permalink | Reply | 4 comments |
headers
Luchesar V. ILIEV | 9 Jan 2011 15:02
Picon
Gravatar

Re: "secondary GPT table is corrupt or invalid" issue again

On 01/09/2011 11:27, Zeus V Panchenko wrote:
> Hi Luchesar,
> 
> thank you for reply,
>>
>> Just my two cents. If I understood correctly from your first mail,
>> you've set up the gmirror on /dev/ada{1,2}p1; that is, you're not
>> mirroring the whole disk, but just the (single) partition on it.
>>
> really the history was this:
> i configured first drive as GPT (whole dedicated drive), newfs-ed it
> and filled with data
> 
> after what i created mirror on it but not on entire disk /dev/ada0 (not on it's
> single partition /dev/ada0p1) and i believe it was the cause of corruption
> 
> latter i found maillist explanation of the mistake and reconfigured
> the mirror to use partitions instead of entire disk ... so, this way
> the corruption appeared as i can judge now 
> 
Ah, that really makes sense now. Actually, a good warning too, as you
wouldn't expect such problems with MBR partitioned disks.

>> have overwritten the secondary GPT. I was wondering if your problem
>> could be related to the ahci(4) driver? I think I've seen reports of
> 
> no, i do not believe it is ahci(4) related issue since no other
> simpthomes were observed (smart data shows no problems too) 
> 
>>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane