What's more, this is already a new controller. It replaced the previous
one because of exactly the same persisting problem. I think tech support
people not knowing a solution just buy some time for them and say "flash
this beta firmware maybe it helps" or "replace your hardware".
We had a
Achilleas Mantzios wrote:
How are you gonna show up in the FreeBSD-* mailing list when you are still on
6.2?
Psst! - I came just here. Don't tell them.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
Friday, April 8, 2011, 1:52:03 PM you wrote:
> Scott Marlowe wrote:
>> If I may ask, how often does it crash? And have you tried updating
>> the firmware of the controller and / or the driver in the OS?
>>
> It happens once per two or three months, or so, taking the average. The
> firmware is bet
Στις Friday 08 April 2011 14:53:58 ο/η Ireneusz Pluta έγραψε:
>
> My general plan for now is to migrate all services from this machine to the
> new ones and refresh it
> completely for use with less critical services. But it is not a task for just
> a few days so the
That's a pain. Migrating
Scott Marlowe wrote:
If I may ask, how often does it crash? And have you tried updating
the firmware of the controller and / or the driver in the OS?
It happens once per two or three months, or so, taking the average. The firmware is beta as of
January this year, advised to use by their technic
Scott Marlowe wrote:
If I may ask, how often does it crash? And have you tried updating
the firmware of the controller and / or the driver in the OS?
It happens once per two or three months, or so, taking the average. The firmware is beta as of
January this year, advised to use by their technic
On 08/04/2011 07:55, Ireneusz Pluta wrote:
Achilleas Mantzios wrote:
In anyway, having FreeBSD to fsck, (background or not) should not
happen. And the problem
becomes bigger when cheap SATA drives will cheat about their write
cache being flushed to the disk.
So in the common case with cheap har
Greg Smith wrote:
The soft update code used in FreeBSD makes sure that there's no damage to the filesystem that
PostgreSQL can't recover from. Once the WAL is replayed after a crash, the database is
consistent. The main purpose of the background fsck is to find "orphaned" space, things that th
On Fri, Apr 8, 2011 at 12:19 AM, Achilleas Mantzios
wrote:
> Στις Friday 08 April 2011 08:55:51 ο/η Ireneusz Pluta έγραψε:
>> Achilleas Mantzios wrote:
>> >
>> > In anyway, having FreeBSD to fsck, (background or not) should not happen.
>> > And the problem
>> > becomes bigger when cheap SATA driv
Στις Friday 08 April 2011 08:55:51 ο/η Ireneusz Pluta έγραψε:
> Achilleas Mantzios wrote:
> >
> > In anyway, having FreeBSD to fsck, (background or not) should not happen.
> > And the problem
> > becomes bigger when cheap SATA drives will cheat about their write cache
> > being flushed to the dis
Achilleas Mantzios wrote:
In anyway, having FreeBSD to fsck, (background or not) should not happen. And
the problem
becomes bigger when cheap SATA drives will cheat about their write cache being
flushed to the disk.
So in the common case with cheap hardware, it is wise to have a UPS connected
On 04/06/2011 06:33 PM, Ireneusz Pluta wrote:
I saw some recommendations from people on the net not to use
background fsck when running PostgreSQL on FreeBSD. As I recall, these
opinions were just thoughts of people which they shared with the
community, following their bad experience caused by
Στις Thursday 07 April 2011 16:31:50 ο/η Ivan Voras έγραψε:
> On 07/04/2011 00:48, Scott Marlowe wrote:
> > On Wed, Apr 6, 2011 at 4:33 PM, Ireneusz Pluta wrote:
> >> Hello,
> >>
> >> I saw some recommendations from people on the net not to use background
> >> fsck
> >> when running PostgreSQL on
On 07/04/2011 00:48, Scott Marlowe wrote:
On Wed, Apr 6, 2011 at 4:33 PM, Ireneusz Pluta wrote:
Hello,
I saw some recommendations from people on the net not to use background fsck
when running PostgreSQL on FreeBSD. As I recall, these opinions were just
thoughts of people which they shared wit
But waiting so much time (like now) during foreground fsck of a large data
filesystem after unclean shutdown, makes me to come to this group to ask
whether I really need to avoid background fsck on a PostgreSQL machine?
Could I hear your opinions?
Shouldn't a journaling file system just come bac
On Wed, Apr 6, 2011 at 4:33 PM, Ireneusz Pluta wrote:
> Hello,
>
> I saw some recommendations from people on the net not to use background fsck
> when running PostgreSQL on FreeBSD. As I recall, these opinions were just
> thoughts of people which they shared with the community, following their bad
Hello,
I saw some recommendations from people on the net not to use background fsck when running PostgreSQL
on FreeBSD. As I recall, these opinions were just thoughts of people which they shared with the
community, following their bad experience caused by using background fsck. So, not coming a
17 matches
Mail list logo
