On Friday 15 July 2005 04:53 pm, Emanuel Strobl wrote:
> Am Freitag, 15. Juli 2005 22:12 CEST schrieb Eirik Øverby:
> > On Jul 15, 2005, at 5:10 PM, Emanuel Strobl wrote:
> > > Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier:
> > >> And, for "the stupid question of the day" ... how lo
David Taylor <[EMAIL PROTECTED]> writes:
>> A corrupted journal can be detected. If it's corrupted, discard
>> the whole thing, or only the relevant entry. The filesystem will
>> remain consistent.
>> If track corruption occurs after the journal is written, it doesn't
>> matter, since at boot the
On Fri, 15 Jul 2005, Matthias Buelow wrote:
> John-Mark Gurney wrote:
>
> >even request barries will not save the fs in a power loss if the track
> >that is getting flushed durning a power loss... Some other FreeBSD
> >folk has a reproducable case of where blocks that were not written to
> >on A
> I know my drive allows disabling of the write cache, as, apparently, the
> majority of IDE/SATA drives do.
Yes fair enough. This command is in the specification as far back as
ata-1. I guess it yields reasonable? performance?
You should, however, be telling sos@ this--if he doesn't already be
Lowell Gilbert <[EMAIL PROTECTED]> writes:
>We keep trying to point out that barriers *can't* be enforced on the
>hardware with many (most, and apparently an increasing percentage of)
>ATA drives. There is no semantic on these drives that allows you to
>guarantee the journal block will be written
"Kevin Oberman" <[EMAIL PROTECTED]> writes:
>I believe that the Windows solution to this problem is to put a really,
>really long delay between when the system is finished syncing and when
>the power is turned off. This might be the best solution for FreeBSD, as
>well, but it will irritate people.
On Fri, 15 Jul 2005, Matthias Buelow wrote:
> Why am I arguing in an uphill battle here? Is data safety no longer
> important to the FreeBSD community? Such issues should not even
> have to be discussed at all!
I'm trying to tell you what you have to say to move forward on this issue:
1) tell p
> Date: Fri, 15 Jul 2005 22:24:07 +0200
> From: Matthias Buelow <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> Wilko Bulte wrote:
>
> > Not If The Bloody PeeCee Style Crap ATA Drives Keep Lying To You..
> >Followups to /dev/null
>
> Yes, makes no sense talking to a wall.
You are right, but
Am Freitag, 15. Juli 2005 22:12 CEST schrieb Eirik Øverby:
> On Jul 15, 2005, at 5:10 PM, Emanuel Strobl wrote:
> > Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier:
> >> And, for "the stupid question of the day" ... how long before 5.x
> >> is no
> >> longer supported? I'm just about
Wilko Bulte wrote:
> Not If The Bloody PeeCee Style Crap ATA Drives Keep Lying To You..
>Followups to /dev/null
Yes, makes no sense talking to a wall.
mkb.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-st
Matthias Buelow <[EMAIL PROTECTED]> writes:
> The combination barriers+journal really seems to be very resilient
> to filesystem corruption. When it's implemented without errors, and
> the hardware doesn't do things like change bits randomly, I can't
> think of a way this scheme can be corrupted a
On Fri, Jul 15, 2005 at 10:11:02PM +0200, Matthias Buelow wrote..
> Chuck Swiger wrote:
>
> >If "sysctl hw.ata.wc=0" doesn't do what you want, please submit a PR
> >containing something better. Or buy SCSI hardware and a real,
>
> Well, if I had the time, I would. Also if instead of softupdate
On Jul 15, 2005, at 5:10 PM, Emanuel Strobl wrote:
Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier:
And, for "the stupid question of the day" ... how long before 5.x
is no
longer supported? I'm just about to deploy a new server, and was
*going* to go with 5.x, but would I be
Chuck Swiger wrote:
>If "sysctl hw.ata.wc=0" doesn't do what you want, please submit a PR
>containing something better. Or buy SCSI hardware and a real,
Well, if I had the time, I would. Also if instead of softupdates,
a proper journalled filesystem implementation with kernel support
for write
While Scott's and Colin's responses should be viewed as canonical, for
the record the place that the support matrix is documented is on the
Security web page at http://www.freebsd.org/security/security.html#adv.
Note that this only applies to the _security_ team. Traditionally the
ports team has
Matthias Buelow wrote:
John-Mark Gurney wrote:
[ ... ]
Why am I arguing in an uphill battle here? Is data safety no longer
important to the FreeBSD community? Such issues should not even
have to be discussed at all!
You ask a good question: so, just why are *you* arguing? [1]
If "sysctl hw.a
John-Mark Gurney wrote:
>even request barries will not save the fs in a power loss if the track
>that is getting flushed durning a power loss... Some other FreeBSD
>folk has a reproducable case of where blocks that were not written to
>on ATA hardware got trashed after a power loss...
>With non-w
John-Mark Gurney wrote:
>With non-written to sectors getting trashed with the cache enabled,
>barriers don't mean squat...
Of course if you pound the disk with a hammer, then barriers also
won't help. Just because with a few disks perhaps it won't work at
all doesn't mean that one shouldn't at le
Matthias Buelow wrote this message on Thu, Jul 14, 2005 at 21:52 +0200:
> >The problem is that disks lie about whether they have actually written
> >data. If the power goes off before the data is in cache, it's lost.
>
> No, the problem is that FreeBSD doesn't implement request barriers
> and that
Bill Vermillion wrote:
>Copying very large files and then shutting down I hope is not a
>normal procecure for you. softupdates sometimes do take a long
>time when you are removing/copying very large files.
>
>Others have suggested different time-outs but you'd have to figure
>out the largest siz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jul 15, 2005 at 04:27:44PM +0100, Yann Golanski wrote:
> Quoth Scott Long on Fri, Jul 15, 2005 at 09:18:50 -0600
> > Part of the purpose of moving quickly on to RELENG_6 is so that the
> > migration work for users from 5.x to 6.x is very small
Hi,
when I mount a device (or medium) which is read-only without
the -r option, I get lots of troubles when shutting down later.
Syncer does not write all vnodes/blocks to disk. This happened
to me with a write protected floppy disk (-t msdos) and a
CD-R (-t ufs).
It seems to me that read-only s
Recently, I started having problems with one of my newest servers ...
figuring that it might have somethign to do with the fact that I went SATA
for this one (all others are SCSI), I figured it might be a driver issue
causing the problems, since everything else is the same as the other 5
serv
Quoth Scott Long on Fri, Jul 15, 2005 at 09:18:50 -0600
> Part of the purpose of moving quickly on to RELENG_6 is so that the
> migration work for users from 5.x to 6.x is very small. 6.x is really
> just an evolutionary step from 5.x, not the life-altering revolutionary
> step that 4.x->5.x was
Marc G. Fournier wrote:
And, for "the stupid question of the day" ... how long before 5.x is no
longer supported? I'm just about to deploy a new server, and was
*going* to go with 5.x, but would I be better just skipping 5.x
altogether? Or are there such drastic changes in 6.x that doing s
Marc G. Fournier wrote:
> And, for "the stupid question of the day" ... how long before 5.x is no
> longer supported?
The FreeBSD Security Team will support FreeBSD 5.x until at least the end
of September 2007. Support from other teams and the ports tree may end
sooner, but since there aren't ver
Am Freitag, 15. Juli 2005 16:58 CEST schrieb Marc G. Fournier:
> And, for "the stupid question of the day" ... how long before 5.x is no
> longer supported? I'm just about to deploy a new server, and was
> *going* to go with 5.x, but would I be better just skipping 5.x
> altogether? Or are there
On Thu, Jul 14, 2005 at 22:31 , [EMAIL PROTECTED]
moved his mouse, rebooted for the change to take effect, and then
said:
> Message: 13
> Date: Thu, 14 Jul 2005 20:38:15 +0200
> From: Anatoliy Dmytriyev <[EMAIL PROTECTED]>
> Subject: dangerous situation with shutdown process
> To: freebsd-stable@
And, for "the stupid question of the day" ... how long before 5.x is no
longer supported? I'm just about to deploy a new server, and was *going*
to go with 5.x, but would I be better just skipping 5.x altogether? Or
are there such drastic changes in 6.x that doing so at this time wouldn't
b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I tried 6.0-BETA on one of our FUJITSU-SIEMENS RX300 S2 servers and
it seems that I have problems with the disk subsystem, even after
Scotts major overhaul of the mpt drivers...
I'm not able to post detailed dmesg output in the moment (IMHO
Hi, I am the fml mailing list manager for <[EMAIL PROTECTED]>.
Hmm, you may be not a member.
1. Your mail may come from a bad address which is not
registered in this mailing list
2. Your mail has a syntax error.
If you would like to subscribe this mailing list
subscribe YOUR NAME
On Fri, Jul 15, 2005 at 12:05:39PM +0200, Marc Olzheim wrote:
> On Fri, Jul 15, 2005 at 11:40:27AM +0200, Marc Olzheim wrote:
> > On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote:
> > > > The -CURRENT traces are very different from these, but I don't have
> > > > comconsole on the -CUR
Am Freitag, den 15.07.2005, 15:10 +0400 schrieb Igor Robul:
> Marc Santhoff wrote:
>
> >Am Freitag, den 15.07.2005, 11:15 +0600 schrieb Sergey N. Voronkov:
> >
> >
> >Intersting, I didn't know these knobs. Would it be okay to set them to
> >zero on an embedded system with r/o file systems?
> >
Marc Santhoff wrote:
Am Freitag, den 15.07.2005, 11:15 +0600 schrieb Sergey N. Voronkov:
Intersting, I didn't know these knobs. Would it be okay to set them to
zero on an embedded system with r/o file systems?
On embeded system with r/o filesystems you may just turn softupdates off.
Announcement
The FreeBSD Release Engineering Team is pleased to announce the
availability of FreeBSD 6.0-BETA1, which marks the beginning of the
FreeBSD 6.0 Release Cycle.
FreeBSD 6.0 will be a much less dramatic step from the FreeBSD 5 branch
than the FreeBSD 5 branch was from Free
Am Freitag, den 15.07.2005, 11:15 +0600 schrieb Sergey N. Voronkov:
> On Thu, Jul 14, 2005 at 04:17:06PM -0400, asym wrote:
> > At 15:19 7/14/2005, Wilko Bulte wrote:
> > >On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote..
> > >> > Date: Thu, 14 Jul 2005 20:38:15 +0200
> > >> > From: A
On Fri, Jul 15, 2005 at 11:40:27AM +0200, Marc Olzheim wrote:
> On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote:
> > > The -CURRENT traces are very different from these, but I don't have
> > > comconsole on the -CURRENT machine.
> >
> > Thanks.
>
> Am I really the only one seeing th
On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote:
> > The -CURRENT traces are very different from these, but I don't have
> > comconsole on the -CURRENT machine.
>
> Thanks.
Since I get plenty of opportunities to fiddle in the debugger now,
because this happens a lot (we use screen a
Hi everybody:
I have a problem with pear:
Last week I tried to upgrade pear-XML_RPC but all that I got was this error:
/usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(678) : ht=0x8182570 is
already destroyed
/usr/ports/lang/php5/work/php-5.0.4/Zend/zend_hash.c(678) : ht=0x8182570 is
alrea
Hello,
I have discontinued using the email address your message was sent to.
Please update your address book with my current email address;
[EMAIL PROTECTED]
and resend any messages that received this reply.
Thank you.
Warren Mosler, Valance Co. Inc.
5000 Estate Southgate, Christiansted, U
40 matches
Mail list logo
