Device (router): WRT54GL
Old firmware: NeoRouter 1.3.0 server on Tomato v1.25
New firmware: NeoRouter 1.7.1 server on Tomato v1.28

I was recently having NeoRouter stability issues with the older firmware, so I decided it was time to upgrade. However, now with the size of my database file (~100kb), it no longer fits on /jffs. I have a sheevaplug on the network with a guest read/writable samba share; the router has this mounted as /cifs1 and I can read/write files to it without a problem. I would like to use cifs1 as the database storage location either directly or via symlinks. Can this be done?

Here are my findings so far:

# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.7M 2.7M 0 100% /
df: proc: No such file or directory
df: ramfs: No such file or directory
- 507.0M 280.9M 226.1M 55% /cifs1
/dev/mtdblock/3 384.0K 324.0K 60.0K 84% /jffs


# ls -l /jffs
lrwxrwxrwx 1 root root 25 Oct 7 15:46 NeoRouter_0_0_1.db -> /cifs1/NeoRouter_0_0_1.db
lrwxrwxrwx 1 root root 17 Oct 7 15:46 server.crt -> /cifs1/server.crt
lrwxrwxrwx 1 root root 17 Oct 7 15:46 server.key -> /cifs1/server.key

# ls -l /cifs1
-rwxr-xr-x 1 root root 102400 Oct 7 17:11 NeoRouter_0_0_1.db
-rw-r----- 1 root root 68608 Oct 20 2010 NeoRouter_0_0_1.db.20121020
-rwxr-xr-x 1 root root 102400 Oct 7 16:54 NeoRouter_0_0_1.db.new
-rw-r--r-- 1 root root 347 Oct 20 2010 nrserver.README
-rwxr-xr-x 1 root root 986 Oct 7 10:35 nrserver.sh
-rw-r--r-- 1 root root 4082 Oct 20 2010 openssl.cnf
-rw-r--r-- 1 root root 1257 Oct 20 2010 server.crt
-rwxr--r-- 1 root root 888 Oct 20 2010 server.key

# /usr/bin/nrserver.sh start
# /usr/bin/nrserver failed to start. [DB]disk I/O error

Even if I remove the database file and attempt a start, it creates a 0 byte .db file on /cifs1...

# rm /cifs1/NeoRouter_0_0_1.db
# /usr/bin/nrserver.sh start
# /usr/bin/nrserver failed to start. [DB]disk I/O error
# ls -l /cifs1/*.db
-rwxr-xr-x 1 root root 0 Oct 7 12:50 NeoRouter_0_0_1.db

I believe this has something to do with the way cifs is mounting the network resource. Some googling reveals similar attempts at mounting database files and requiring "nobrl" as a cifs option. However, so far attempts at remounting with it enabled result in:

Oct 7 21:50:42 ? user.warn kernel: CIFS: Unknown mount option nobrl