On Fri, Dec 28, 2012 at 01:27:24PM +0200, Konstantin Belousov wrote:
Please try the following patch. It is against HEAD, might need some
adjustments for 8. I do the resume and write accounting atomically,
not allowing other suspension to intervent between.
So is this only limited to snapshot
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
db alltrace (pid 18 and 7126)
Tracing command g_journal switcher pid 18 tid 100076 td 0xff0002bd5000
sched_switch() at sched_switch+0xde
mi_switch() at mi_switch+0x186
sleepq_wait() at
On Fri, Dec 28, 2012 at 10:19:31AM +0100, Andreas Longwitz wrote:
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
db alltrace (pid 18 and 7126)
Tracing command g_journal switcher pid 18 tid 100076 td 0xff0002bd5000
sched_switch() at
Konstantin Belousov wrote:
Please try the following patch. It is against HEAD, might need some
adjustments for 8. I do the resume and write accounting atomically,
not allowing other suspension to intervent between.
diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c
index
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J in
lists.freebsd.org/pipermail/freebsd-current/2012-January/030937.html.
The snapshot was initiated by amanda with
dump 3ubLshf 64 1048576 0 - /dev/mirror/gm0p10.journal (pid
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J in
lists.freebsd.org/pipermail/freebsd-current/2012-January/030937.html.
The snapshot was initiated by amanda
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J in
lists.freebsd.org/pipermail/freebsd-current/2012-January/030937.html
On Thu, Dec 27, 2012 at 06:47:05PM +0100, Andreas Longwitz wrote:
Konstantin Belousov wrote:
On Thu, Dec 27, 2012 at 12:28:54PM +0100, Andreas Longwitz wrote:
On a FreeBSD 8-Stable machine with UFS + GJOURNAL (no SU) I observed the
same behaviour as described for UFS+SU+J
Hello,
We've experienced a weird data rollback on our NFS servers.
We have two NFS servers. Both running 8.3-RELEASE-p3. We've
setup HAST for one partition between both of them. To be able
to switch fast we configured gjournal on top of HAST. At the
time there was no UFS+J.
Yesterday one
Hello, Eugene.
You wrote 9 сентября 2011 г., 9:17:06:
# fsck -t ffs -y /dev/mirror/gm0.journals1e
I may be wrong, but I've encountered strong advice not
to gjournal whole disk, but make gjournal on per-FS basis, many times.
And it seems, that your first create big journal, and splice
09.09.2011 15:21, Lev Serebryakov пишет:
Hello, Eugene.
You wrote 9 сентября 2011 г., 9:17:06:
# fsck -t ffs -y /dev/mirror/gm0.journals1e
I may be wrong, but I've encountered strong advice not
to gjournal whole disk, but make gjournal on per-FS basis, many times.
And it seems
Hello, Eugene.
You wrote 9 сентября 2011 г., 13:40:51:
# fsck -t ffs -y /dev/mirror/gm0.journals1e
I may be wrong, but I've encountered strong advice not
to gjournal whole disk, but make gjournal on per-FS basis, many times.
And it seems, that your first create big journal, and splice
Dear Pawel Jakub,
09.09.2011 12:17, Eugene Grosbein writes:
Hi!
For long time I experience same UFS2 filesystem problems with several 8.2
systems
running on gmirror+gjournal+async. In case of unclean shutdown, kernel panic
or power failure
gjournal makes fsck skip its checks and that's
on gjournal provider. You configured slices and several
pratitions on one gjournal provider, which simply cannot work, as
one UFS file system has to talk to one gjournal provider.
If not, mounting such UFS2 should warn us, shouldn't it?
No warnings now.
It might be a bit hard to tell, but it could
No. It will only work properly for journaling UFS if UFS is placed
directory on gjournal provider. You configured slices and several
pratitions on one gjournal provider, which simply cannot work, as
one UFS file system has to talk to one gjournal provider.
If not, mounting such UFS2 should warn us
Hi!
For long time I experience same UFS2 filesystem problems with several 8.2
systems
running on gmirror+gjournal+async. In case of unclean shutdown, kernel panic or
power failure
gjournal makes fsck skip its checks and that's why I use it.
But quite often my /var partition (and sometimes
8388608 3 (null) (4.0G)
2432696354 497580781 4 backup (237G)
gjournal label /dev/gpt/storage /dev/gptid/3570dff6-9a73-11e0-ad0e-001e8c0ecc19
gjournal label /dev/gpt/backup /dev/gptid/58db2577-9a73-11e0-ad0e-001e8c0ecc19
newfs -J /dev/gpt/storage.journal
newfs -J /dev/gpt
On 20.06.2011 13:17, nickolas...@gmail.com wrote:
How can I mount this partitions using GPT labels?
Hi,
i think the only way to do it is use hardcoded provider name
when you are configuring journal.
--
WBR, Andrey V. Elsukov
signature.asc
Description: OpenPGP digital signature
storage (1.1T)
2424307746 8388608 3 (null) (4.0G)
2432696354 497580781 4 backup (237G)
gjournal label /dev/gpt/storage /dev/gptid/3570dff6-9a73-11e0-ad0e-001e8c0ecc19
gjournal label /dev/gpt/backup /dev/gptid/58db2577-9a73-11e0-ad0e-001e8c0ecc19
newfs -J /dev/gpt
2 storage (1.1T)
2424307746 8388608 3 (null) (4.0G)
2432696354 497580781 4 backup (237G)
gjournal label /dev/gpt/storage
/dev/gptid/3570dff6-9a73-11e0-ad0e-001e8c0ecc19
gjournal label /dev/gpt/backup /dev/gptid/58db2577-9a73-11e0-ad0e-001e8c0ecc19
newfs -J /dev
Bengt Ahlgren ben...@sics.se wrote:
nickolas...@gmail.com writes:
I've tried to make two journaled partitions on new GPT disk.
...
How can I mount this partitions using GPT labels?
...
I think the idea with labels is great, but whether it works or
not seems pretty random to me as a user.
Hello, freebsd-geom.
On FreeBSD 8.2-RELEASE long periods of «Suspend time» have been detected
- tens of seconds - while reading large files from gjournal partition:
For example:
root@mail [/var/tmp]# du -h /var/tmp/access.log
8.3G /var/tmp/access.log
root@mail[/var/tmp]# dd if=/var/tmp
the gmirror creation process (module in /boot/loader.conf,
the modified fstab... all) and all is correct. I suspect some
gjournal+gmirror especial issues maybe
¿Any clue?
FreeBSD 7.2 AMD64
--
I must not fear. Fear is the mind-killer. Fear is the little-death that
brings total obliteration. I
configuration. One of the threads:
http://markmail.org/message/tamo4r2jho3zdv3z
In the described crash, similar error messages were seen, but with
error=1. Ultimately Pawel Dawidek (gjournal author) gave the
diagnosis that the crash was related to the first filesystem in the
slice being set up
)
/dev/ad6s1f on /var (ufs, local)
Thanks!
-Garrett
GJournal actually doesn't work on your box now. To make it work,
you MUST use special flag -J to newfs. See beginning of newfs(8).
After you do newfs -O2 -J /dev/ad6s1d.journal and mount it,
you will see somehow different mount output
.
- gjournal label -f ad6s1d ad6s2d
- mount /dev/ad6s1d /usr # That works (I think...), but prints out the
error message below:
GEOM_JOURNAL: [flush] Error while writing data (error=1)
ad6s2d[WRITE(offset=512, length=6656)]
gjournal status says:
Name Status Components
.
- gjournal label -f ad6s1d ad6s2d
- mount /dev/ad6s1d /usr # That works (I think...), but prints out the
error message below:
GEOM_JOURNAL: [flush] Error while writing data (error=1)
ad6s2d[WRITE(offset=512, length=6656)]
gjournal status says:
Name Status Components
with a minimal distribution. This creates
/usr // /dev/ad6s1d as UFS2 with softupdates disabled.
- Pull latest stable sources. Rebuild kernel (with `options
GEOM_JOURNAL'), world, install kernel, then world after reboot.
- gjournal label -f ad6s1d ad6s2d
- mount /dev/ad6s1d /usr # That works (I
with a minimal distribution. This creates
/usr // /dev/ad6s1d as UFS2 with softupdates disabled.
- Pull latest stable sources. Rebuild kernel (with `options
GEOM_JOURNAL'), world, install kernel, then world after reboot.
- gjournal label -f ad6s1d ad6s2d
- mount /dev/ad6s1d /usr # That works (I
FreeBSD 7.2-RELEASE
GPT + gmirror + gjournal
May 31 10:15:48 netserv1 kernel: Fatal trap 9: general protection
fault while in kernel mode
May 31 10:15:48 netserv1 kernel: cpuid = 0; apic id = 00
May 31 10:15:48 netserv1 kernel: instruction pointer= 0x8:0x8059f667
May 31 10:15:48
2009/6/2 David N david...@gmail.com:
FreeBSD 7.2-RELEASE
GPT + gmirror + gjournal
May 31 10:15:48 netserv1 kernel: Fatal trap 9: general protection
fault while in kernel mode
May 31 10:15:48 netserv1 kernel: cpuid = 0; apic id = 00
May 31 10:15:48 netserv1 kernel: instruction pointer
I'm using a GJournal on top of GRAID3 on top of GPart.
What happens:
If I go to my gjournal mount point e put:
dd if=/dev/zero of=file bs=1k count=10
The system freeze. No more response in the corrent ssh session, the
system don't respond to new ssh connection, and the console got
freezed too
Haven't been able to make it lock up today.
I'll recompile the kernel on both machines with
options KDB
options DDB
and let it run with the workload and see if it locks up again.
I'm sorry about the noise.
Regards
David N
___
I managed to get the server to lock up again.
It responds to ping
Top was still running
last pid: 42052; load averages: 0.00, 0.16, 0.19
up 0+15:27:29 09:32:08
135 processes: 1 running, 93 sleeping, 41 waiting
CPU: 0.0% user, 0.0% nice, 0.4% system, 0.0% interrupt,
Hi,
I've got gjournal on two computers running 7.2-RELEASE (AMD64 and
i386) both with SATA-I. (150)
GPT + GMirror + GJournal
I've had it soft lock, locking up with no HDD activity. And can't do
anything, except a hard reset. on both machines.
Box1 (i386) removed a slow HDD and replaced
2009/5/25 Ivan Voras ivo...@freebsd.org:
David N wrote:
Hi,
I've got gjournal on two computers running 7.2-RELEASE (AMD64 and
i386) both with SATA-I. (150)
GPT + GMirror + GJournal
I've had it soft lock, locking up with no HDD activity. And can't do
anything, except a hard reset. on both
David N wrote:
The first time it locked up was when i was copying
cp -va
from one disk (degraded mirrror) to the other disk (degraded mirror +
gjournal). Copied around 40GB until it locked up. It did it 3 times
before i manage to copy everything over. Re-syncing of the mirror
works fine
2009/5/25 Ivan Voras ivo...@freebsd.org:
David N wrote:
The first time it locked up was when i was copying
cp -va
from one disk (degraded mirrror) to the other disk (degraded mirror +
gjournal). Copied around 40GB until it locked up. It did it 3 times
before i manage to copy everything over
David N wrote:
2009/5/25 Ivan Voras ivo...@freebsd.org:
David N wrote:
The first time it locked up was when i was copying
cp -va
from one disk (degraded mirrror) to the other disk (degraded mirror +
gjournal). Copied around 40GB until it locked up. It did it 3 times
before i manage to copy
Ivan Voras wrote:
David N wrote:
2009/5/25 Ivan Voras ivo...@freebsd.org:
David N wrote:
The first time it locked up was when i was copying
cp -va
from one disk (degraded mirrror) to the other disk (degraded mirror +
gjournal). Copied around 40GB until it locked up. It did it 3 times
before
2009/5/25 Ivan Voras ivo...@freebsd.org:
David N wrote:
2009/5/25 Ivan Voras ivo...@freebsd.org:
David N wrote:
The first time it locked up was when i was copying
cp -va
from one disk (degraded mirrror) to the other disk (degraded mirror +
gjournal). Copied around 40GB until it locked up
Marat N.Afanasyev wrote:
usually when disc subsystem locks no program can be launched neither
top, nor ps ;) i'd rather use ^T while cp hang
Depending on where it's stuck. You can start top before it locks up
and leave it running. If it's only the low levels that are stuck,
precaching ps will
Jeremy Chadwick wrote:
On Sun, Aug 03, 2008 at 12:14:36AM +0200, Eugene Butusov wrote:
2) smartctl -a /dev/ad4
...
198 Offline_Uncorrectable 0x0030 100 253 000Old_age Offline -
0
200 Multi_Zone_Error_Rate 0x0008 100 253 051Old_age Offline -
0
2008/8/3 Eugene Butusov [EMAIL PROTECTED]:
Hi,
Recently I've decided to play with gjournal. Main reason was a promise of
avoiding full fsck check after unclean shutdown. I've successfuly configured
gjournal on existing filesystems (all UFS). And then it happened - my system
had a power
David N wrote:
2008/8/3 Eugene Butusov [EMAIL PROTECTED]:
Hi,
Recently I've decided to play with gjournal. Main reason was a promise of
avoiding full fsck check after unclean shutdown. I've successfuly configured
gjournal on existing filesystems (all UFS). And then it happened - my system
had
On Sun, Aug 03, 2008 at 12:36:33PM +0200, Eugene Butusov wrote:
Jeremy Chadwick wrote:
On Sun, Aug 03, 2008 at 12:14:36AM +0200, Eugene Butusov wrote:
2) smartctl -a /dev/ad4
...
198 Offline_Uncorrectable 0x0030 100 253 000Old_age Offline
- 0
200
, an existing partition
EB
EB umount /home
EB gjournal label -f /dev/ad4s1g
EB tunefs -J enable -n disable /dev/ad4s1g.journal
EB (added 'async' option to /etc/fstab for /home and changed entry to
EB /dev/ad4s1g.journal)
EB mount /home
EB
EB It worked until power failed... :)
No surprize. with you
/ad4s1g is my /home, an existing partition
EB
EB umount /home
EB gjournal label -f /dev/ad4s1g
EB tunefs -J enable -n disable /dev/ad4s1g.journal
EB (added 'async' option to /etc/fstab for /home and changed entry to
EB /dev/ad4s1g.journal)
EB mount /home
EB
EB It worked until power failed
Hi,
Recently I've decided to play with gjournal. Main reason was a
promise of avoiding full fsck check after unclean shutdown. I've
successfuly configured gjournal on existing filesystems (all UFS). And
then it happened - my system had a power failure. After boot, it
forced me to run fsck
On Sat, Aug 02, 2008 at 11:15:25PM +0200, Eugene Butusov wrote:
Aug 2 19:13:43 matrix kernel: ** /dev/ad4s1g.journal
Aug 2 19:13:43 matrix kernel:
Aug 2 19:13:43 matrix kernel: CANNOT READ BLK: 727112224
Aug 2 19:13:43 matrix kernel: CONTINUE? [yn]
Aug 2 19:13:43 matrix kernel:
Aug 2
(don't even dare telling you) and that let it give some quite random errors.
So you might want to do some real good hardware checks ;)
-- Jille
Eugene Butusov schreef:
Hi,
Recently I've decided to play with gjournal. Main reason was a promise
of avoiding full fsck check after unclean shutdown
Jeremy Chadwick wrote:
On Sat, Aug 02, 2008 at 11:15:25PM +0200, Eugene Butusov wrote:
Aug 2 19:13:43 matrix kernel: ** /dev/ad4s1g.journal
Aug 2 19:13:43 matrix kernel:
Aug 2 19:13:43 matrix kernel: CANNOT READ BLK: 727112224
Aug 2 19:13:43 matrix kernel: CONTINUE? [yn]
Aug 2 19:13:43
On Sun, Aug 03, 2008 at 12:14:36AM +0200, Eugene Butusov wrote:
2) smartctl -a /dev/ad4
...
198 Offline_Uncorrectable 0x0030 100 253 000Old_age Offline
- 0
200 Multi_Zone_Error_Rate 0x0008 100 253 051Old_age Offline
- 0
...
The other SMART
on RELENG_7 as of June 28th:
sunny:RabbitsDen./expand_number 5368709120k
Result is 1099511627776
sunny:RabbitsDen./expand_number 5120G
Result is 5497558138880
sunny:RabbitsDen
One of the more interesting manifestations in the userland is that
gjournal label -s 5368709120 -f /dev/da0s1a
5368709120k
Result is 1099511627776
sunny:RabbitsDen./expand_number 5120G
Result is 5497558138880
sunny:RabbitsDen
One of the more interesting manifestations in the userland is that
gjournal label -s 5368709120 -f /dev/da0s1a
quietly gives you 1G of the journal in the resulting file system
is 5497558138880
sunny:RabbitsDen
One of the more interesting manifestations in the userland is that
gjournal label -s 5368709120 -f /dev/da0s1a
quietly gives you 1G of the journal in the resulting file system.
Cut here---
#include ctype.h
I have started experimenting with gjournal filesystems this weekend. I found
something that may be a mistake I made. Not sure.
To break up my IDE drive into the filesystems I wanted I created multiple
slices. On slice 2 I had multiple gjournal filesystems. I tried creating a
journal
Hi,
after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64
(built from latest CVS source), the box hung a couple of times when on high
disk load. Finally, while building some port it won't boot for no reason
obvious to me.
This is what I get with kernel.geom.mirror.debug
On 12/23/-58 20:59, Michael Harris wrote:
Hi,
after one month with gmirror and gjournal running on a 7.0-RELEASE #p2 amd64
(built from latest CVS source), the box hung a couple of times when on high
disk load. Finally, while building some port it won't boot for no reason
obvious to me
is then
carved up by bsdlabel into gm0a (/), gm0b (swap), gm0d (/var), gm0e
(/tmp), and gm0f (/usr).
My latest machine is using Seagate 1TB disks so I thought I should add
gjournal to the mix to avoid ugly fsck's if/when the machine doesn't
shut down cleanly. I ended up just creating a gm0f.journal
device (gm0), which is then
carved up by bsdlabel into gm0a (/), gm0b (swap), gm0d (/var), gm0e
(/tmp), and gm0f (/usr).
My latest machine is using Seagate 1TB disks so I thought I should add
gjournal to the mix to avoid ugly fsck's if/when the machine doesn't
shut down cleanly. I ended up just
Adam McDougall writes:
[...]
I believe gjournal uses 1G for journal (2x512) which seemed to be
sufficient on all of the systems where I have used the default, but I
quickly found that using a smaller journal is a bad idea and leads to
panics that I was unable to avoid with tuning
Adam McDougall writes:
George Hartzell wrote:
[...]
- I've read in the gjournal man page that when it is ... configured
on top of gmirror(8) or graid3(8) providers, it also keeps them in
a consistent state... I've been trying to figure out if this
simply falls out
George Hartzell wrote:
Adam McDougall writes:
George Hartzell wrote:
[...]
- I've read in the gjournal man page that when it is ... configured
on top of gmirror(8) or graid3(8) providers, it also keeps them in
a consistent state... I've been trying to figure out
* Karl Denninger [EMAIL PROTECTED] [080329 20:10] wrote:
Hi folks;
Wondering about the various pros and cons of using the gjournal GEOM
provider... and if you can promote and existing system using it, or
whether you need to build something anew.
The scenario is a fairly busy and large
On Sun, Mar 30, 2008 at 02:06:17AM -0700, Alfred Perlstein wrote:
* Karl Denninger [EMAIL PROTECTED] [080329 20:10] wrote:
Hi folks;
Wondering about the various pros and cons of using the gjournal GEOM
provider... and if you can promote and existing system using it, or
whether you need
and gjournal both provide for meta data consistency,
something that a database rarely needs as it rarely creates/deletes
files often.
I'm looking at this more from a performance standpoint.
Is there a performance advantage to using gjournal over a normal UFS/UFS2
filesystem with softupdates
Karl Denninger wrote:
Is there a performance advantage to using gjournal over a normal UFS/UFS2
filesystem with softupdates?
Short answer - no. Long answer - maybe, in very specific scenarios which
are probably not possible in real world usage.
For PostgreSQL and similar advanced databases
Hi folks;
Wondering about the various pros and cons of using the gjournal GEOM
provider... and if you can promote and existing system using it, or
whether you need to build something anew.
The scenario is a fairly busy and large system with PostgreSQL database data
on it. The data is currently
I am evaluating using gjournal on my servers. This one test system is
running 7.0-RELEASE at the moment on a Dell PE2650 with dual 2ghz xeon,
ahc0: Adaptec aic7899 Ultra160 SCSI adapter, and some seagate 36g 10k
disks. I had the opportunity to try placing the journal consumer device
On Thu, Mar 13, 2008 at 05:57:41PM -0400, Adam McDougall wrote:
I am evaluating using gjournal on my servers. This one test system is
running 7.0-RELEASE at the moment on a Dell PE2650 with dual 2ghz xeon,
ahc0: Adaptec aic7899 Ultra160 SCSI adapter, and some seagate 36g 10k
snip
tuning guides and recomendations, and signs Beware!
Dragons are here! Hey, are FreeBSD experimental system or production
one?!
Ok, ZFS (gjournal, whatever) need more resources (memory, journal
space, whatever) and system is mis-tuned and can not provide this
resource (in case of ZFS and 32bit
and the work involved in configuring
it properly I decided to newfs the drives again to ufs + soft updates
something that is faster and just works, googling shows there seems to
be very few people using gjournal so is still a bit immature for
stable status in my view.
Chris
I had originally enabled gjournal and seemed to have no problems but I
was seeing errors in messages regarding dma write failures and after
some research concluded I had setup gjournal incorrectly.
I setup the gjournal again properly with soft updates disabled and
doing a fresh newfs, mount
Chris wrote:
Came back to see box had rebooted itself from a journal related panic.
panic: Journal overflow (joffset=49905408 active=499691355136 inactive=4990$
cpuid = 0
AFAIK this means that the journal is too small for your machine - try
doubling it until there are no more panics.
the journal to the data area.
Is there something stopping gjournal from temporarily blocking writes
to the journal to allow it to flush the journaled data to the provider?
Thanks,
Gary
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org
experimentation with gjournal a few weeks ago to determine
how I might partition
a new server, as well as how large to make my journals and where. I did
find that for the computers
I have tested so far, a 1 gig (default size) journal seems to be
sufficient, but half of that or less is
asking for trouble
I did some experimentation with gjournal a few weeks ago to determine
how I might partition
a new server, as well as how large to make my journals and where. I did
find that for the computers
I have tested so far, a 1 gig (default size) journal seems to be
sufficient, but half
AFAIK this means that the journal is too small for your machine - try
doubling it until there are no more panics.
If so, this is the same class of errors as ZFS (some would call it
tuning errors), only this time the space reserved for the on-disk
journal is too small, and the fast drives
be
transfered from the journal to the data area.
Is there something stopping gjournal from temporarily blocking writes
to the journal to allow it to flush the journaled data to the provider?
I've done something like that in the past, but I don't know if Pawel's
gjournal has this implemented.
I feel
Chris wrote:
If the only advantage of journaling is to avoid slow fsck's then I may
decide I can live without it, the real attraction to me was been able
to use the much glamorised async which is what made me so shocked when
write speeds were low.
If I understood this thread correctly, the
If I understood this thread correctly, the impression of poor
performance is based on a configuration where both the journal and the
data are on the same physical drive. Intuitively, this will likely
penalize any transaction on the volume, read or write, since you're
asking the drive to not
Michael Butler wrote:
I would think that journaling on one drive and storing the resultant
data-set on another would improve performance enormously (reduced
seek-lengths) and more so if they were 1) high-rpm drives (less
rotational latency) and 2) on different buses (no bus/controller
Chris wrote:
AFAIK this means that the journal is too small for your machine - try
doubling it until there are no more panics.
If so, this is the same class of errors as ZFS (some would call it
tuning errors), only this time the space reserved for the on-disk
journal is too small, and the fast
Hi everyone,
In my laptop, I am running 7.0 Beta-4 (today's kernel + world). my /usr (ad0s1f
) is using gjournal, with its journal on ad0s1h .
I have it mounted with what I believe are the recommended settings:
$ mount
[...]
/dev/ad0s1f.journal on /usr (ufs, asynchronous, local, noatime
Hello!
I have an IBM System x3400 machine with IBM ServeRAID 8k controller. There
are three RAID1 volumes on the controller, which the OS sees as aacd0,
aacd1 and aacd2. aacd1 contains three slices, aacd1s1 is simple UFS2,
aacd1s2 and aacd1s3 are using UFS2 with gjournal.
When I was using
Forgot to mention, I'm running amd64.
--
Toomas Aas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Toomas Aas wrote:
kernel: GEOM_JOURNAL: Journal 161627211: aacd1s2 contains data.
kernel: GEOM_JOURNAL: Journal 161627211: aacd1s2 contains journal.
kernel: GEOM_JOURNAL: Journal aacd1s2 clean.
kernel: GEOM_JOURNAL: Journal 3372893522: aacd1s3 contains data.
kernel: GEOM_JOURNAL: Journal
Toomas Aas wrote:
kernel: GEOM_JOURNAL: Journal 3372893522: aacd1s3G EcOoMn_tJaOiUnRsN
AdLa:t aB.IO
kernel: _GFELOUMS_HJ OnUoRtN AsLu:p pJoorutrenda lb y 3a3a7c2d819s325.22
Looking more closely at this 'garbage' I just noticed that this is actually
two messages 'mixed' together.
If you
I built a machine with 6.2 snapshot from April (May/June would not
boot). I used the original src with the gjournal patch. I had to
manually patch mount.h and vnode.h to complete the patch. everything
built and installed fine and my gjournal seems to be working (gjournal
loaded and gstats
Hi all,
I have a setup on 6-STABLE from today with two identical disks in
a gm0 provider and 3 gjournal providers on it:
Geom name: gm0
State: COMPLETE
Components: 2
Balance: round-robin
Slice: 1
Flags: NONE
GenID: 0
SyncID: 1
ID: 2763081532
Václav Haisman wrote:
Hi,
I have experimentally installed PJD's GEOM Journal patch on 6.2. It seems to
work except that I got deadlock tonight, probably during periodic snapshot.
Post mortem ps output is attached.
Definitely repeatable, tonight it locked up again.
--
VH
signature.asc
Hi,
I have experimentally installed PJD's GEOM Journal patch on 6.2. It seems to
work except that I got deadlock tonight, probably during periodic snapshot.
Post mortem ps output is attached.
--
VH
pidproc uid ppid pgrp flag stat comm wchan
97212 c26a64300 41639 97212
Václav Haisman wrote:
Hi,
yesterday, I tried to build kernel and world with the gjournal patch. It
does not apply cleanly. This brings me to question, are there some
outstanding issues that prevent it from being commited to RELENG_6? I
tried to search ml archives but I did not find any
Václav Haisman wrote:
Hi,
yesterday, I tried to build kernel and world with the gjournal patch. It
does not apply cleanly. This brings me to question, are there some
outstanding issues that prevent it from being commited to RELENG_6? I
tried to search ml archives but I did not find any
Hi all,
I was intending on trying out gjournal on a new disk i've added in my
desktop. I had a look to see what the most recent patch provided by
Pawel and found
http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch
I created the directories as per Pawel's original post
(http
Philippe Pegon wrote:
Vince wrote:
Hi all,
Hi,
I was intending on trying out gjournal on a new disk i've added in my
desktop. I had a look to see what the most recent patch provided by
Pawel and found
http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch
I created
Kramer wrote:
I've already redone the whole thing. here are the steps i took
umount /scr09
umount /scr10
gjournal stop da2.journal
gjournal stop da4.journal
** had not done this on the first attempt
newfs /dev/da1
newfs /dev/da3
This is not needed.
gjournal label -v /dev/da2 /dev/da1
think journaling relies on the same assumptions.
Not gjournal, because it uses BIO_FLUSH I/O requests which flushes disk
write cache when needed.
--
Pawel Jakub Dawidek http://www.wheel.pl
[EMAIL PROTECTED] http://www.FreeBSD.org
FreeBSD committer
Pawel Jakub Dawidek wrote:
- todays desktop drives can lie about writing data. SoftUpdates relies
on some assumptions about when the data is physically written to
media, and those are not always valid today
I think journaling relies on the same assumptions.
Not gjournal, because
1 - 100 of 124 matches
Mail list logo
