on 27/04/2010 09:00 Jeff Roberson said the following:
> I think some people are enabling after returning to single user from a
> live system rather than booting into single user. This is a different
> path in the filesystem as booting directly just mounts read-only while
> the other option updates
On 27 April 2010 10:01, Jeff Roberson wrote:
> On Mon, 26 Apr 2010, pluknet wrote:
>
>> On 26 April 2010 17:42, dikshie wrote:
>>>
>>> Hi Jeff,
>>> thanks for SUJ.
>>> btw, why there is nan% utilization? and what does it mean?
>>> --
>>> ** SU+J Recovering /dev/ad0s1g
>>> ** Reading 3
On Mon, 26 Apr 2010, pluknet wrote:
On 26 April 2010 17:42, dikshie wrote:
Hi Jeff,
thanks for SUJ.
btw, why there is nan% utilization? and what does it mean?
--
** SU+J Recovering /dev/ad0s1g
** Reading 33554432 byte journal from inode 4.
** Building recovery table.
** Resolving u
On Sun, 25 Apr 2010, Bruce Cran wrote:
On Sunday 25 April 2010 19:47:00 Scott Long wrote:
On Apr 24, 2010, at 8:57 PM, Jeff Roberson wrote:
On Sun, 25 Apr 2010, Alex Keda wrote:
try in single user mode:
tunefs -j enable /
tunefs: Insuffient free space for the journal
tunefs: soft updates jou
On Sun, 25 Apr 2010, Scott Long wrote:
On Apr 24, 2010, at 8:57 PM, Jeff Roberson wrote:
On Sun, 25 Apr 2010, Alex Keda wrote:
try in single user mode:
tunefs -j enable /
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not be enabled
tunefs -j enable /dev/a
On Sun, 25 Apr 2010, Gary Jennejohn wrote:
On Sat, 24 Apr 2010 16:57:59 -1000 (HST)
Jeff Roberson wrote:
On Sun, 25 Apr 2010, Alex Keda wrote:
try in single user mode:
tunefs -j enable /
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not be enabled
tunef
On Sun, 25 Apr 2010, Lucius Windschuh wrote:
Hi Jeff,
thank you for your effort in implementing the soft update journaling.
I tried to test SUJ on a provider with 4 kB block size. My system runs
9-CURRENT r207195 (i386).
Unfortunately, tunefs is unable to cope with the device. It can easily
repr
On Mon, 26 Apr 2010, Vladimir Grebenschikov wrote:
Hi
First, many thanks for this effort, it is really very appreciated,
Panic on Gnome starting:
Thank you for the report with stack. That was very helpful. I know how
to fix this bug but it will take me a day or two as my primary test
mac
On 26 April 2010 17:42, dikshie wrote:
> Hi Jeff,
> thanks for SUJ.
> btw, why there is nan% utilization? and what does it mean?
> --
> ** SU+J Recovering /dev/ad0s1g
> ** Reading 33554432 byte journal from inode 4.
> ** Building recovery table.
> ** Resolving unreferenced inode list.
Hi
First, many thanks for this effort, it is really very appreciated,
Panic on Gnome starting:
# kgdb -q /usr/obj/usr/src/sys/VBOOK/kernel.debug /var/crash/vmcore.12
...
#0 doadump () at pcpu.h:246
246 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) x/s panicstr
0xc07c2160 :
on 26/04/2010 16:42 dikshie said the following:
> Hi Jeff,
> thanks for SUJ.
> btw, why there is nan% utilization? and what does it mean?
0/0 I guess. Floating point allows that :-)
> --
> ** SU+J Recovering /dev/ad0s1g
> ** Reading 33554432 byte journal from inode 4.
> ** Building re
Hi Jeff,
thanks for SUJ.
btw, why there is nan% utilization? and what does it mean?
--
** SU+J Recovering /dev/ad0s1g
** Reading 33554432 byte journal from inode 4.
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
** 0 journal records in 0
Hi Jeff,
thank you for your effort in implementing the soft update journaling.
I tried to test SUJ on a provider with 4 kB block size. My system runs
9-CURRENT r207195 (i386).
Unfortunately, tunefs is unable to cope with the device. It can easily
reproduced with these steps:
# mdconfig -s 128M -S
On Sunday 25 April 2010 19:47:00 Scott Long wrote:
> On Apr 24, 2010, at 8:57 PM, Jeff Roberson wrote:
> > On Sun, 25 Apr 2010, Alex Keda wrote:
> >> try in single user mode:
> >>
> >> tunefs -j enable /
> >> tunefs: Insuffient free space for the journal
> >> tunefs: soft updates journaling can no
On Apr 24, 2010, at 8:57 PM, Jeff Roberson wrote:
> On Sun, 25 Apr 2010, Alex Keda wrote:
>
>> try in single user mode:
>>
>> tunefs -j enable /
>> tunefs: Insuffient free space for the journal
>> tunefs: soft updates journaling can not be enabled
>>
>> tunefs -j enable /dev/ad0s2a
>> tunefs: In
On Sat, 24 Apr 2010 16:57:59 -1000 (HST)
Jeff Roberson wrote:
> On Sun, 25 Apr 2010, Alex Keda wrote:
>
> > try in single user mode:
> >
> > tunefs -j enable /
> > tunefs: Insuffient free space for the journal
> > tunefs: soft updates journaling can not be enabled
> >
> > tunefs -j enable /dev/a
Jeff Roberson wrote:
On Sun, 25 Apr 2010, Alex Keda wrote:
try in single user mode:
tunefs -j enable /
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not be enabled
tunefs -j enable /dev/ad0s2a
tunefs: Insuffient free space for the journal
tunefs: soft updat
On Sun, 25 Apr 2010, Alex Keda wrote:
try in single user mode:
tunefs -j enable /
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not be enabled
tunefs -j enable /dev/ad0s2a
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not
On Tuesday 20 April 2010 23:15:48 Jeff Roberson wrote:
> Hi Folks,
>
> You may have seen my other Soft-updates journaling (SUJ) announcements.
> If not, it is a journaling system that works cooperatively with
> soft-updates to eliminate the full background filesystem check after an
> unclean shutd
try in single user mode:
tunefs -j enable /
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not be enabled
tunefs -j enable /dev/ad0s2a
tunefs: Insuffient free space for the journal
tunefs: soft updates journaling can not be enabled
tunefs: /dev/ad0s2a: failed t
On Wed, 21 Apr 2010, Garrett Cooper wrote:
On Wed, Apr 21, 2010 at 12:39 AM, Gary Jennejohn
wrote:
On Tue, 20 Apr 2010 12:15:48 -1000 (HST)
Jeff Roberson wrote:
Hi Folks,
You may have seen my other Soft-updates journaling (SUJ) announcements.
If not, it is a journaling system that works co
On Wed, Apr 21, 2010 at 12:39 AM, Gary Jennejohn
wrote:
> On Tue, 20 Apr 2010 12:15:48 -1000 (HST)
> Jeff Roberson wrote:
>
>> Hi Folks,
>>
>> You may have seen my other Soft-updates journaling (SUJ) announcements.
>> If not, it is a journaling system that works cooperatively with
>> soft-updates
On Tue, 20 Apr 2010 12:15:48 -1000 (HST)
Jeff Roberson wrote:
> Hi Folks,
>
> You may have seen my other Soft-updates journaling (SUJ) announcements.
> If not, it is a journaling system that works cooperatively with
> soft-updates to eliminate the full background filesystem check after an
> u
On Tue, 20 Apr 2010, Patrick Tracanelli wrote:
Jeff Roberson escreveu:
Hi Folks,
You may have seen my other Soft-updates journaling (SUJ) announcements.
If not, it is a journaling system that works cooperatively with
soft-updates to eliminate the full background filesystem check after an
uncle
On Wed, Apr 21, 2010 at 00:15, Jeff Roberson wrote:
> Hi Folks,
>
> You may have seen my other Soft-updates journaling (SUJ) announcements. If
> not, it is a journaling system that works cooperatively with soft-updates to
> eliminate the full background filesystem check after an unclean shutdown.
Jeff Roberson escreveu:
> Hi Folks,
>
> You may have seen my other Soft-updates journaling (SUJ) announcements.
> If not, it is a journaling system that works cooperatively with
> soft-updates to eliminate the full background filesystem check after an
> unclean shutdown. SUJ may be enabled with t
Hi Folks,
You may have seen my other Soft-updates journaling (SUJ) announcements.
If not, it is a journaling system that works cooperatively with
soft-updates to eliminate the full background filesystem check after an
unclean shutdown. SUJ may be enabled with tunefs -j enable and disabled
wi
27 matches
Mail list logo
