I need to test my web app in a scenario where there’s no disk space remaining, i.e. I cannot write any more files. But I don’t want to fill my hard drive with junk just to make sure there’s really no space left. What I want is to simulate this situation withing a particular process (actually, a PHP app).
Indeed, temporarily prohibiting disk writes to a process must be enough.
What’s the easiest way to do this? I’m using Mac OS X 10.6.2 with built-in Apache/PHP bundle. Thanks.
Edit : Disk free space check is not going to be reliable since it can change any moment. Many pages are being served simultaneously. There can be enough free space when checking, but none by the moment you actually write something. Also, checking for disk free space will require changing the code everywhere I write a file, which is not what I want :-) Finally, this solution is exactly the opposite of what I’m trying to test: how my app will behave when it cannot write any more.
Source: Tips4all
I bet you could also create your own .dmg file with file system of size ... say 2Mb and write to it. If this works, then it is super-easy for testing - you just mount it and switch the path for testing. If the dmg is small enough, you could probably even upload it to the source control.
ReplyDeleteWhen I needed to do this I created a virtual machine with limited space allocated to the virtual disk.
ReplyDeleteNo need to use a prefilled dummy filesystem.
ReplyDeleteUse disk_free_space() to mock the FileSystem
disk_free_space() - Given a string containing a directory,
this function will return the number
of bytes available on the
corresponding filesystem or disk
partition.
To simulate, just wrap the function into a FileSystem Class. Then inject it to your class doing the saving as a dependency and check if the drive is full before you do the actual saving. In your UnitTest, just swap out the regular class with the class mocking a full file system and you're done. This way you don't have to recreate the full disk drive or keep the drive with your project files all the time whenever you want to rerun your test, e.g.
class MyFileSystem
{
public static function df($drive)
{
return disk_free_space($drive);
}
}
and to simulate a full FileSystem do
class MyFileSystemFull
{
public static function df($drive)
{
return 0;
}
}
If you want to overload the function to return 0 at all times, you could use the RunKit Pecl extension and do:
runkit_function_redefine('disk_free_space','string','return 0;');
As an alternative look into vfsStream:
vfsStream is a stream wrapper for a virtual file system that may be helpful in unit tests to mock the real file system. It can be used with any unit test framework, like PHPUnit or SimpleTest.
I used a thumb drive, as the volume for the process.
ReplyDeleteI'm not sure of how to do it on OSX but on Linux, I'd probably put a disk quota on my test user and then run the app.
ReplyDeleteOr maybe create a null file (a small one), format it as an ext3 partition, mount it using the loopback device and run the PHP app inside it. This would be closer to a physical disk that's short of space.
A quick and easy solution would be setting up a Quota for a specialized user account. Quota support on Mac OS X
ReplyDeleteIf you don't mind the hassle to set it up, and the fact that you probably need a second license for your operating system, a Virtual Machine is probably the best idea with the most long-term possibilities.
Create a disk/filesystem image in a regular file (of limited size) and loop mount it.
ReplyDeleteBut if you'll be doing this often I'd create a virtual machine—you'll find opportunity to reuse it.
Can't you use a Mock, and substitute the part of your code which actually writes to disk, with a fake test replacement which will throw the exception(s) you expect to see?
ReplyDeleterecursively remove all write permissions from your webfolder, folders and files your app is going to write to.
ReplyDeleteBottom line; don't do that. Seriously -- there are so many things that go horribly wrong when a volume runs out of space. Unless the volume targeted is not the boot volume and has not one other application writing to it, the behavior as the disk fills will be out of your control anyway.
ReplyDeleteIf it is the boot drive, the system will quite likely panic or crash upon full disk anyway. Or, if not, it'll behave erratically.
If you are talking about a data volume, is yours the only app that is writing to it? If any other app is writing, do you know for certain how they might fail?
Disk space is so dirt cheap these days that you are far better off ensuring that out of disk space will simply never happen. Drop a 2TB drive in and put an alarm in when it reaches 50% capacity. Far cheaper to implement (unless your time is free) and far more reliable.
Have you tried mount with -f -r ? It's not really low disk space, but it should throw an error from the same level.
ReplyDeleteI think the idea with the mock class is the right direction. I usually test my code that way too. If possible I use a framework for that though, instead of writing those classes myself. I don't know PHP very well (more programming with C# and Java) , but this seems to be nice.
ReplyDeletehttps://github.com/padraic/mockery
Wherever you obtain the remaining disk space, just comment it out and run your app with a replacement values such as 0.1, 0, -1
ReplyDelete