Error while reading drive info for path /var/lib/eventstore. Message: The drive name does not exist

EventStoreDB
1

Gday,

I’m having a similar problem to this post: https://groups.google.com/d/topic/event-store/XXgGJ8GBjgE/discussion however I’m not sure how y’all feel about necroposting, so made a new post.

I’m running ES 3.4.0 in clustered docker containers, based off ubuntu 14.04.4:

ES VERSION: 3.4.0.0 (release-ha-v3.4.0/58dcb0af4d4d267469021cb2aa7334c20a9ac8bd, Thu, 17 Dec 2015 10:31:33 +0200)

OS: Linux (Unix 4.2.2.2)

RUNTIME: 3.12.1 (tarball) (64-bit)

GC: 2 GENERATIONS

LOGS: /var/log/eventstore

–db option is the default (/var/lib/eventstore); I installed eventstore-oss=3.4.0, so the user exists, the path exists, the path is owned by the user, and the container is running as the user. Is looks as though the path is event being written correctly:

core@core-01 ~ $ docker exec 4d0f20f8ff71 whoami

eventstore

core@core-01 ~ $ docker exec 4d0f20f8ff71 ls -la /var/lib/eventstore

total 604

drwxr-xr-x. 1 eventstore eventstore 4096 Mar 13 08:53 .

drwxr-xr-x. 1 root root 4096 Mar 12 07:35 …

-rw-r–r--. 1 eventstore eventstore 8 Mar 13 09:11 chaser.chk

-rw-r–r--. 1 eventstore eventstore 268435712 Mar 13 09:11 chunk-000000.000000

-rw-r–r--. 1 eventstore eventstore 8 Mar 13 08:54 epoch.chk

drwxr-xr-x. 2 eventstore eventstore 4096 Mar 13 08:53 index

-rw-r–r--. 1 eventstore eventstore 8 Mar 13 08:53 truncate.chk

-rw-r–r--. 1 eventstore eventstore 8 Mar 13 09:11 writer.chk

I am still, however, periodically (every 30s) getting the error:

Error while reading drive info for path /var/lib/eventstore. Message: The drive name does not exist

Parameter name: driveName.

Is this maybe normal behaviour for System.IO.DriveInfo under linux, or in docker? Is there a way to get more debug info on why this is coming up?

Cheers,

Brenton.

2

var driveInfo = ShellExecutor.GetOutput("df", string.Format("-P {0}",
directory));

3

Hi Greg,

I assume this is a line I should add to the method I linked to, then compile, then run this? I’m afraid I’m not too familiar with working with mono source.

Is the output from df -P /var/lib/eventstore sufficient? On docker, it gives:

core@core-01 ~ $ docker exec 4d0f20f8ff71 df -P /var/lib/eventstore

Filesystem 1024-blocks Used Available Capacity Mounted on

overlay 16326556 759368 14704692 5% /

whereas on an ubuntu 14.04 EC2 box it gives:

ubuntu@ip-192-168-1-236:~$ df -hP /var/lib/eventstore/

Filesystem Size Used Avail Use% Mounted on

/dev/xvdb1 79G 56M 75G 1% /var/lib/eventstore

I suppose the overlay filesystem is what throws the error on the version running under docker?

4

I see that the line you posted is in the GetDirectoryRootInUnix method of that class; in the docker case this method should return “/”, and being an overlay filesystem shouldn’t have any impact.

So that leaves me at still not knowing where this error might come from.

I did just notice that I missed the head of the error messages:

[00006,113,03:58:49.969] Error while reading drive info for path /var/lib/eventstore. Message: The drive name does not exist

Parameter name: driveName.

[00006,119,03:59:21.100] Error while reading drive info for path /var/lib/eventstore. Message: The drive name does not exist

Parameter name: driveName.

[00006,81,03:59:52.205] Error while reading drive info for path /var/lib/eventstore. Message: The drive name does not exist

Parameter name: driveName.

[00006,13,04:00:23.334] Error while reading drive info for path /var/lib/eventstore. Message: The drive name does not exist

Parameter name: driveName.

Is the 00006 helpful at all in finding where this error is being thrown?

5

Bump. Any ideas? I’m pretty sure I’m not the only who is going to have this issue, if it’s docker related.

6

Also having that pop up in the Event Store log on my Docker container. Doesn’t seem to stop ES from running, though.

7

In case anyone else falls into the groups blackhole from google there’s a related issue here. https://github.com/EventStore/EventStore/issues/1536