Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run on an empty partition #2

Closed
dcabro opened this issue Dec 27, 2012 · 5 comments
Closed

Can't run on an empty partition #2

dcabro opened this issue Dec 27, 2012 · 5 comments
Assignees

Comments

@dcabro
Copy link

dcabro commented Dec 27, 2012

stressdisk on windows will not run on an empty partition. It reports "Couldn't read directory "X:": open X:: Access is denied."

As soon as I created one empty directory, it runs without problems. I run this from elevated prompt (with admin rights).

@ghost ghost assigned ncw Dec 28, 2012
@ncw
Copy link
Owner

ncw commented Dec 28, 2012

Was the partition formatted? Stressdisk can't run on an unformatted partition which I should probably make clearer in the docs.

I tried to reproduce this with an empty network share (with VirtualBox) and I ran

stressdisk run y:

And it worked OK. How can I reproduce the problem?

@dcabro
Copy link
Author

dcabro commented Dec 31, 2012

Yes it was formatted ( I read the instructions before trying to use it).

Well, in order to reproduce the issue, you'd probably need to have
exactly the same setup, e.g. local empty formatted disk under Win7 64bit.

Like I described, as soon as I created one empty directory, it started
running. I've even tried to delete the directory (and have empty
partition) and to run it again to verify - and i threw an error.

I managed to check my disk so I'm fine, but just wanted you to know in
case someone else will have this problem as well.

Thanks for the great tool!

Cheers

On 12/28/2012 4:06 PM, Nick Craig-Wood wrote:

Was the partition formatted? Stressdisk can't run on an unformatted
partition which I should probably make clearer in the docs.

I tried to reproduce this with an empty network share (with VirtualBox)
and I ran

|stressdisk run y:
|

And it worked OK. How can I reproduce the problem?


Reply to this email directly or view it on GitHub
#2 (comment).

@ncw
Copy link
Owner

ncw commented Dec 31, 2012

I've got hold of a real Windows 7 machine now and I've managed to reproduce the issue.

I think this is an issue in go which I've reported: http://code.google.com/p/go/issues/detail?id=4601

We'll see what the go developers think though!

In the mean time I'll try to make a work-around

@ncw ncw closed this as completed in eddf47b Dec 31, 2012
@ncw
Copy link
Owner

ncw commented Dec 31, 2012

This should be fixed now!

Re-open if you still see a problem

If you want your real name in the changelog then let me know what it is

Thanks for the bug report and glad you find it a useful tool

Nick

@dcabro
Copy link
Author

dcabro commented Jan 1, 2013

Great to hear that!

No problem and thanks again!

Cheers,
Darko

Понедельник, 31 декабря 2012, 4:47 -08:00 от Nick Craig-Wood notifications@github.com:

This should be fixed now!
Re-open if you still see a problem
If you want your real name in the changelog then let me know what it is
Thanks for the bug report and glad you find it a useful tool
Nick

Reply to this email directly or view it on GitHub .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants