Prev: sys.sql_expression_dependencies bug?
Next: Problem with SOAP Toolkit and web service authorization
From: Ian Boyd on 6 Jan 2009 17:05
i'm trying to expand my transaction log file from 7,000MB to 14,000MB

Enterprise Manager reports:

Error 5149: MODIFY FILE encountered operating system error
112(There is not enough space on the disk.) while attempting to
expand the physical file.

The partition the database, and log, is on (F:) has 46GB free.
The other partition (C:) has 30GB free.

Both partitions are formatted NTFS.

The Event Log shows nothing else of note, except an event from SQL Server
that that the log is full.

The database is in Simple mode.

Using process explorer, the entire attempt to expand the log causes 3 file
operations:
1. SetPositionInformationFile (Position: 14,680,064,000), SUCCESS
2. QueryPositionInformationFile (Position: 14,680,064, 000), SUCCESS
3. SetEndOfFileInformationFiile (EndOfFile: 14,680,064,000), DISK FULL

The database files are
CMSArchive.mdf is 64,185,344 KiB
CMSArchive_Log.ldf is 7.207,296 KiB

What is going on?

From: Chuck Heinzelman on 6 Jan 2009 18:39
Ian-

I ran into something similar when someone turned on disk quotas on a
development server I was working with. Have you checked that yet?

Sincerely,

Chuck Heinzelman
SQL Server MVP

"Ian Boyd" <ian.msnews(a)avatopia.com> wrote in message
news:99C21CEC-F475-4A70-9D6B-4F49757BF23D(a)microsoft.com...
> i'm trying to expand my transaction log file from 7,000MB to 14,000MB
>
> Enterprise Manager reports:
>
> Error 5149: MODIFY FILE encountered operating system error
> 112(There is not enough space on the disk.) while attempting to
> expand the physical file.
>
> The partition the database, and log, is on (F:) has 46GB free.
> The other partition (C:) has 30GB free.
>
> Both partitions are formatted NTFS.
>
> The Event Log shows nothing else of note, except an event from SQL Server
> that that the log is full.
>
> The database is in Simple mode.
>
> Using process explorer, the entire attempt to expand the log causes 3 file
> operations:
> 1. SetPositionInformationFile (Position: 14,680,064,000), SUCCESS
> 2. QueryPositionInformationFile (Position: 14,680,064, 000), SUCCESS
> 3. SetEndOfFileInformationFiile (EndOfFile: 14,680,064,000), DISK FULL
>
> The database files are
> CMSArchive.mdf is 64,185,344 KiB
> CMSArchive_Log.ldf is 7.207,296 KiB
>
> What is going on?

From: Ian Boyd on 7 Jan 2009 09:07
i have not. And honestly, i wouldn't even know how :)

But the problem fixed itself, so i guess i, and this guy:
http://www.developersdex.com/sql/message.asp?p=580&r=6376678
will never find a solution.

> Ian-
>
> I ran into something similar when someone turned on disk quotas on a
> development server I was working with. Have you checked that yet?
>
> Sincerely,
>
> Chuck Heinzelman
> SQL Server MVP

From: Ian Boyd on 7 Jan 2009 09:10
i installed Debugging Tools for Windows, and configured Process Monitor with
the appropriate symbol path.

The next attempt worked.

i guess either
a) 13th time's the charm.
b) a watched process never fails



"Ian Boyd" <ian.msnews(a)avatopia.com> wrote in message
news:99C21CEC-F475-4A70-9D6B-4F49757BF23D(a)microsoft.com...
> i'm trying to expand my transaction log file from 7,000MB to 14,000MB
>
> Enterprise Manager reports:
>
> Error 5149: MODIFY FILE encountered operating system error
> 112(There is not enough space on the disk.) while attempting to
> expand the physical file.
>
> The partition the database, and log, is on (F:) has 46GB free.
> The other partition (C:) has 30GB free.
>
> Both partitions are formatted NTFS.
>
> The Event Log shows nothing else of note, except an event from SQL Server
> that that the log is full.
>
> The database is in Simple mode.
>
> Using process explorer, the entire attempt to expand the log causes 3 file
> operations:
> 1. SetPositionInformationFile (Position: 14,680,064,000), SUCCESS
> 2. QueryPositionInformationFile (Position: 14,680,064, 000), SUCCESS
> 3. SetEndOfFileInformationFiile (EndOfFile: 14,680,064,000), DISK FULL
>
> The database files are
> CMSArchive.mdf is 64,185,344 KiB
> CMSArchive_Log.ldf is 7.207,296 KiB
>
> What is going on?

From: Ian Boyd on 7 Jan 2009 09:17
And for posterity:

SELECT @@version
-----------------------------
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)



 | 
Pages: 1
Prev: sys.sql_expression_dependencies bug?
Next: Problem with SOAP Toolkit and web service authorization