headers
FreeBSD bugmaster | 4 Aug 2008 13:06
Picon
Favicon

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

Current FreeBSD problem reports
Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s kern/73177   geom       kldload geom_* causes panic due to memory exhaustion
o kern/84556   geom       [geom] GBDE-encrypted swap causes panic at shutdown
o kern/87544   geom       [gbde] mmaping large files on a gbde filesystem deadlo
s kern/89102   geom       [geom] [panic] panic when forced unmount FS from unplu
o kern/89546   geom       [geom] GEOM error
a kern/89660   geom       [vinum] [patch] [panic] due to g_malloc returning null
o bin/90093    geom       fdisk(8) incapable of altering in-core geometry
o kern/90582   geom       [geom] [panic] Restore cause panic string (ffs_blkfree
o kern/98034   geom       [geom] dereference of NULL pointer in acd_geom_detach 
o kern/104389  geom       [geom] [patch] sys/geom/geom_dump.c doesn't encode XML
o kern/113419  geom       [geom] geom fox multipathing not failing back
o kern/113957  geom       [gmirror] gmirror is intermittently reporting a degrad
o kern/120021  geom       net-p2p/qbittorrent crashes system when it works thoug
o kern/120231  geom       [geom] GEOM_CONCAT error adding second drive
o kern/121364  geom       [gmirror] Removing all providers create a "zombie" mir
o kern/122067  geom       [panic]: Geom crashed during boot
f kern/122415  geom       [geom] UFS labels are being constantly created and rem
o kern/123122  geom       [geom] GEOM / gjournal kernel lock
o kern/123962  geom       [panic] gjournal(8): gjournal (455Gb data, 8Gb journal
o kern/124130  geom       [gmirror][usb] gmirror fails to start usb devices that
o kern/124294  geom       [geom] gmirror(8) have inappropriate logic when workin
o kern/124969  geom       gvinum(8): gvinum raid5 plex does not detect missing s

22 problems total.
(Continue reading)

Permalink | Reply | 0 comments |
headers
FreeBSD bugmaster | 11 Aug 2008 13:06
Picon
Favicon

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

Current FreeBSD problem reports
Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s kern/73177   geom       kldload geom_* causes panic due to memory exhaustion
o kern/84556   geom       [geom] GBDE-encrypted swap causes panic at shutdown
o kern/87544   geom       [gbde] mmaping large files on a gbde filesystem deadlo
s kern/89102   geom       [geom] [panic] panic when forced unmount FS from unplu
o kern/89546   geom       [geom] GEOM error
a kern/89660   geom       [vinum] [patch] [panic] due to g_malloc returning null
o bin/90093    geom       fdisk(8) incapable of altering in-core geometry
o kern/90582   geom       [geom] [panic] Restore cause panic string (ffs_blkfree
o kern/98034   geom       [geom] dereference of NULL pointer in acd_geom_detach 
o kern/104389  geom       [geom] [patch] sys/geom/geom_dump.c doesn't encode XML
o kern/113419  geom       [geom] geom fox multipathing not failing back
o kern/113957  geom       [gmirror] gmirror is intermittently reporting a degrad
o kern/120021  geom       net-p2p/qbittorrent crashes system when it works thoug
o kern/120231  geom       [geom] GEOM_CONCAT error adding second drive
o kern/121364  geom       [gmirror] Removing all providers create a "zombie" mir
o kern/122067  geom       [panic]: Geom crashed during boot
f kern/122415  geom       [geom] UFS labels are being constantly created and rem
o kern/123122  geom       [geom] GEOM / gjournal kernel lock
o kern/123962  geom       [panic] gjournal(8): gjournal (455Gb data, 8Gb journal
o kern/124130  geom       [gmirror][usb] gmirror fails to start usb devices that
o kern/124294  geom       [geom] gmirror(8) have inappropriate logic when workin
o kern/124969  geom       gvinum(8): gvinum raid5 plex does not detect missing s

22 problems total.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Valerio Daelli | 13 Aug 2008 15:52
Picon

Status of gjournal

Hi

we would like to use a gjournaled filesystem on FreeBSD 7.0.
We plan to use a ciss or mpt controller.
Is there any plan to implement the BIO_FLUSH request in these
drivers?
Is it safe to create a gjournal on those controllers as is?
Thanks

Valerio Daelli
Permalink | Reply | 0 comments |
headers
FreeBSD bugmaster | 18 Aug 2008 13:06
Picon
Favicon

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

Current FreeBSD problem reports
Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s kern/73177   geom       kldload geom_* causes panic due to memory exhaustion
o kern/84556   geom       [geom] GBDE-encrypted swap causes panic at shutdown
o kern/87544   geom       [gbde] mmaping large files on a gbde filesystem deadlo
s kern/89102   geom       [geom] [panic] panic when forced unmount FS from unplu
o kern/89546   geom       [geom] GEOM error
a kern/89660   geom       [vinum] [patch] [panic] due to g_malloc returning null
o bin/90093    geom       fdisk(8) incapable of altering in-core geometry
o kern/90582   geom       [geom] [panic] Restore cause panic string (ffs_blkfree
o kern/98034   geom       [geom] dereference of NULL pointer in acd_geom_detach 
o kern/104389  geom       [geom] [patch] sys/geom/geom_dump.c doesn't encode XML
o kern/113419  geom       [geom] geom fox multipathing not failing back
o kern/113957  geom       [gmirror] gmirror is intermittently reporting a degrad
o kern/120021  geom       net-p2p/qbittorrent crashes system when it works thoug
o kern/120231  geom       [geom] GEOM_CONCAT error adding second drive
o kern/121364  geom       [gmirror] Removing all providers create a "zombie" mir
o kern/122067  geom       [panic]: Geom crashed during boot
f kern/122415  geom       [geom] UFS labels are being constantly created and rem
o kern/123122  geom       [geom] GEOM / gjournal kernel lock
o kern/123962  geom       [panic] gjournal(8): gjournal (455Gb data, 8Gb journal
o kern/124130  geom       [gmirror][usb] gmirror fails to start usb devices that
o kern/124294  geom       [geom] gmirror(8) have inappropriate logic when workin
o kern/124969  geom       gvinum(8): gvinum raid5 plex does not detect missing s

22 problems total.
(Continue reading)

Permalink | Reply | 0 comments |
headers
FreeBSD bugmaster | 25 Aug 2008 13:06
Picon
Favicon

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

Current FreeBSD problem reports
Critical problems
Serious problems

S Tracker      Resp.      Description
--------------------------------------------------------------------------------
s kern/73177   geom       kldload geom_* causes panic due to memory exhaustion
o kern/84556   geom       [geom] GBDE-encrypted swap causes panic at shutdown
o kern/87544   geom       [gbde] mmaping large files on a gbde filesystem deadlo
s kern/89102   geom       [geom] [panic] panic when forced unmount FS from unplu
o kern/89546   geom       [geom] GEOM error
a kern/89660   geom       [vinum] [patch] [panic] due to g_malloc returning null
o bin/90093    geom       fdisk(8) incapable of altering in-core geometry
o kern/90582   geom       [geom] [panic] Restore cause panic string (ffs_blkfree
o kern/98034   geom       [geom] dereference of NULL pointer in acd_geom_detach 
o kern/104389  geom       [geom] [patch] sys/geom/geom_dump.c doesn't encode XML
o kern/113419  geom       [geom] geom fox multipathing not failing back
o kern/113957  geom       [gmirror] gmirror is intermittently reporting a degrad
o kern/120021  geom       net-p2p/qbittorrent crashes system when it works thoug
o kern/120231  geom       [geom] GEOM_CONCAT error adding second drive
o kern/121364  geom       [gmirror] Removing all providers create a "zombie" mir
o kern/122067  geom       [panic]: Geom crashed during boot
f kern/122415  geom       [geom] UFS labels are being constantly created and rem
o kern/123122  geom       [geom] GEOM / gjournal kernel lock
o kern/123962  geom       [panic] gjournal(8): gjournal (455Gb data, 8Gb journal
o kern/124130  geom       [gmirror][usb] gmirror fails to start usb devices that
o kern/124294  geom       [geom] gmirror(8) have inappropriate logic when workin
o kern/124969  geom       gvinum(8): gvinum raid5 plex does not detect missing s

22 problems total.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brian McCann | 28 Aug 2008 16:05
Picon

gjournal & fsck

Hi all.  I'm having some problems with several servers I've built
recently (7.0-RELEASE) that are using gjournal.  I had two reboot a
few days ago (un-related to FreeBSD problems I think)...but when they
came back up, the file systems wouldn't mount since they were not
clean.  Now, I understand that UFS knows nothing about the fact that
it's journaled, and the journaling knows nothing about UFS...but it's
my understanding that by using gjournal, you should really never need
to fsck a file system.  However, the only way to get them to mount is
by doing the fsck.  Is there something else I should be doing instead
of fsck?

And since I know it will probably come up, I built the file systems
using the instructions and notes at
http://www.freebsd.org/cgi/man.cgi?query=gjournal&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html.

Any help would be greatly appreciated!
Thanks!
--Brian

--

-- 
_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_-=-_
Brian McCann

"I don't have to take this abuse from you -- I've got hundreds of
people waiting to abuse me."
 -- Bill Murray, "Ghostbusters"
_______________________________________________
freebsd-questions <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"
(Continue reading)

Permalink | Reply | 26 comments |
headers
Ivan Voras | 28 Aug 2008 16:34
Picon
Favicon
Gravatar

Re: gjournal & fsck

Brian McCann wrote:
> Hi all.  I'm having some problems with several servers I've built
> recently (7.0-RELEASE) that are using gjournal.  I had two reboot a
> few days ago (un-related to FreeBSD problems I think)...but when they
> came back up, the file systems wouldn't mount since they were not
> clean.  Now, I understand that UFS knows nothing about the fact that
> it's journaled, and the journaling knows nothing about UFS...but it's

Actually UFS needs to know about gjournal for just this purpose. There's
a special option to newfs that tells the file system to be aware of
gjournal and it should request fscks.

> my understanding that by using gjournal, you should really never need
> to fsck a file system.  However, the only way to get them to mount is
> by doing the fsck.  Is there something else I should be doing instead
> of fsck?

man 8 tunefs
Permalink | Reply | 18 comments |
headers
Brian McCann | 28 Aug 2008 16:43
Picon

Re: gjournal & fsck

On Thu, Aug 28, 2008 at 10:34 AM, Ivan Voras <ivoras <at> freebsd.org> wrote:
> Brian McCann wrote:
>> Hi all.  I'm having some problems with several servers I've built
>> recently (7.0-RELEASE) that are using gjournal.  I had two reboot a
>> few days ago (un-related to FreeBSD problems I think)...but when they
>> came back up, the file systems wouldn't mount since they were not
>> clean.  Now, I understand that UFS knows nothing about the fact that
>> it's journaled, and the journaling knows nothing about UFS...but it's
>
> Actually UFS needs to know about gjournal for just this purpose. There's
> a special option to newfs that tells the file system to be aware of
> gjournal and it should request fscks.
>
>> my understanding that by using gjournal, you should really never need
>> to fsck a file system.  However, the only way to get them to mount is
>> by doing the fsck.  Is there something else I should be doing instead
>> of fsck?
>
> man 8 tunefs
>

Yes...I apologize...I did that when I built the file system with
"newfs -J".  Here's the tunefs -p output for one of the file systems:

# tunefs -p /dev/da2.journal
tunefs: ACLs: (-a)                                         disabled
tunefs: MAC multilabel: (-l)                               disabled
tunefs: soft updates: (-n)                                 disabled
tunefs: gjournal: (-J)                                     enabled
tunefs: maximum blocks per file in a cylinder group: (-e)  2048
(Continue reading)

Permalink | Reply | 16 comments |
headers
Manolis Kiagias | 28 Aug 2008 16:44
Picon
Gravatar

Re: gjournal & fsck

Brian McCann wrote:
> Hi all.  I'm having some problems with several servers I've built
> recently (7.0-RELEASE) that are using gjournal.  I had two reboot a
> few days ago (un-related to FreeBSD problems I think)...but when they
> came back up, the file systems wouldn't mount since they were not
> clean.  Now, I understand that UFS knows nothing about the fact that
> it's journaled, and the journaling knows nothing about UFS...but it's
> my understanding that by using gjournal, you should really never need
> to fsck a file system.  However, the only way to get them to mount is
> by doing the fsck.  Is there something else I should be doing instead
> of fsck?
>
> And since I know it will probably come up, I built the file systems
> using the instructions and notes at
> http://www.freebsd.org/cgi/man.cgi?query=gjournal&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html.
>
> Any help would be greatly appreciated!
> Thanks!
> --Brian
>
>   

You may wish to have a look at this article:

http://www.freebsd.org/doc/en_US.ISO8859-1/articles/gjournal-desktop

In particular, you should make sure you use tunefs to enable Journaling 
and disable soft update on the journaled filesystems, i.e.:

tunefs -J enable -n disable /dev/ad0s1f.journal
(Continue reading)

Permalink | Reply | 4 comments |
headers
Ivan Voras | 28 Aug 2008 16:51
Picon
Favicon
Gravatar

Re: gjournal & fsck

Brian McCann wrote:

> Yes...I apologize...I did that when I built the file system with
> "newfs -J".  Here's the tunefs -p output for one of the file systems:
> 
> # tunefs -p /dev/da2.journal
> tunefs: ACLs: (-a)                                         disabled
> tunefs: MAC multilabel: (-l)                               disabled
> tunefs: soft updates: (-n)                                 disabled
> tunefs: gjournal: (-J)                                     enabled
> tunefs: maximum blocks per file in a cylinder group: (-e)  2048
> tunefs: average file size: (-f)                            16384
> tunefs: average number of files in a directory: (-s)       64
> tunefs: minimum percentage of free space: (-m)             8%
> tunefs: optimization preference: (-o)                      time
> tunefs: volume label: (-L)
> 
> I'm concerned about this because the ones I've had problems with
> recently are 1.1TB arrays...I've got 2 8.6TB arrays that are journaled
> as well...and if I ever have to fsck them...that could take 1/2 the
> day...
> 
> Any other thoughts?

Ok.

There was one person that complained about fsck on gjournal but not in
the same context - he created the journal for gjournal on an existing
file system and so destroyed a part of the data. I don't think this is
related to your case.
(Continue reading)

Permalink | Reply | 12 comments |

Gmane