[DataFileSync] FlushViewOfFile failed 33 file

[Ed Rooth]

Keep getting this error on 1.6.5 windows 64-bit.

I noticed there's a JIRA issue, but haven't heard anything recently. 

Is this going to cause problems? 

Anything we can do to fix it?

Thanks.

[Nat]

I guess you can safely ignore it most of the time. It looks like you
can get it if fsync is called when O/S is flushing the pages itself.

On Feb 13, 7:43 pm, Ed Rooth <ed.ro...@gmail.com> wrote:
> Keep getting this error on 1.6.5 windows 64-bit.

> I noticed there's a JIRA issue <http://jira.mongodb.org/browse/SERVER-1163>,

[Gaetan Voyer-Perrault]

Hello Ed;

It looks like you've followed-up on the JIRA ticket. 

Is this error causing the server to crash outright? Is the error just something in the logs?

Is any of the data corrupted or is everything still running?

Is it easy to reproduce? It sounds like you're just doing lots and lots of inserts, is that correct?

You say you're getting 44k inserts / second. Are you planning to constantly write  at that rate or is this just an initial data dump?

- Gates

--
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com.
To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mongodb-user?hl=en.

[Ed Rooth]

Hi Gates,

No crashes, just errors in the log. 

Everything seems to still be running ok. The server continues to run with no indication of corruption. 

It pretty much happens anytime we add an index to our collection (which is currently about 20 gb). 

That's not us doing the 44k writes, that's the guy who originally created the bug report. We're not doing any writes, just adding indexes. 

Thanks,

Ed

[Gates]

Hello Ed;

If you're not getting any corruption, then you can just keep running.

However, I would appreciate if you could file a new JIRA bug with
details of what you're seeing (server version, log files, data size).
http://jira.mongodb.org/

At the least this will help us clean-up the error or provide more
cogent logging for future users.

- Gates

On Feb 13, 3:09 pm, Ed Rooth <ed.ro...@gmail.com> wrote:
> Hi Gates,
>
> No crashes, just errors in the log.
>
> Everything seems to still be running ok. The server continues to run with no indication of corruption.
>
> It pretty much happens anytime we add an index to our collection (which is currently about 20 gb).
>
> That's not us doing the 44k writes, that's the guy who originally created the bug report. We're not doing any writes, just adding indexes.
>
> Thanks,
> Ed
>
> On Feb 14, 2011, at 7:08 AM, Gaetan Voyer-Perrault <ga...@10gen.com> wrote:
>
>
>
>
>
>
>
> > Hello Ed;
>
> > It looks like you've followed-up on the JIRA ticket.
>
> > Is this error causing the server to crash outright? Is the error just something in the logs?
>
> > Is any of the data corrupted or is everything still running?
>
> > Is it easy to reproduce? It sounds like you're just doing lots and lots of inserts, is that correct?
>
> > You say you're getting 44k inserts / second. Are you planning to constantly write  at that rate or is this just an initial data dump?
>
> > - Gates
>

> > On Sun, Feb 13, 2011 at 5:45 AM, Nat <nat.lu...@gmail.com> wrote:
> > I guess you can safely ignore it most of the time. It looks like you
> > can get it if fsync is called when O/S is flushing the pages itself.
>
> > On Feb 13, 7:43 pm, Ed Rooth <ed.ro...@gmail.com> wrote:
> > > Keep getting this error on 1.6.5 windows 64-bit.
> > > I noticed there's a JIRA issue <http://jira.mongodb.org/browse/SERVER-1163>,
> > > but haven't heard anything recently.
>
> > > Is this going to cause problems?
> > > Anything we can do to fix it?
>
> > > Thanks.
>
> > --
> > You received this message because you are subscribed to the Google Groups "mongodb-user" group.
> > To post to this group, send email to mongod...@googlegroups.com.
> > To unsubscribe from this group, send email to mongodb-user...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/mongodb-user?hl=en.

[Ed Rooth]

Thanks Gates.

Here's the bug

http://jira.mongodb.org/browse/SERVER-2553