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

unrecoverable crash #153

Open
crodwell opened this issue Dec 1, 2017 · 2 comments
Open

unrecoverable crash #153

crodwell opened this issue Dec 1, 2017 · 2 comments

Comments

@crodwell
Copy link

crodwell commented Dec 1, 2017

Hi, still having an unrecoverable crash issue intermittently. I cannot restart riofs without first running an umount on the directory. I managed to harvest a verbose log right before a crash; not sure it's of any help:

16:28:23 [dir_tree] (dir_tree_file_write dir_tree.c:1529) [ino: 19999, fop: 0x1701c60] write inode, size: 4096, off: 938463232
16:28:23 [fio] (fileio_write_buffer file_io_ops.c:581) [ino: 19999] Write buf size: 5234688
16:28:23 [cmng] (cache_mng_store_file_buf cache_mng.c:381) [ino: 19999] Written [938463232:4096] bytes, result: OK
16:28:23 [fuse] (rfuse_write_cb rfuse.c:717) [req: 0x2e3c460] write_cb success: YES
16:28:23 [dir_tree] (dir_tree_on_buffer_written_cb dir_tree.c:1475) [ino: 19999, fop: 0x1701c60] Buffer written, count: 4096
16:28:23 [fuse] (rfuse_write rfuse.c:732) [ino: 20028, fi: 0x7ffee81d5780] write inode, size: 4096, off: 52482048
16:28:23 [dir_tree] (dir_tree_file_write dir_tree.c:1529) [ino: 20028, fop: 0x54d22b0] write inode, size: 4096, off: 52482048
16:28:23 [fio] (fileio_write_buffer file_io_ops.c:581) [ino: 20028] Write buf size: 53248
16:28:23 [cmng] (cache_mng_store_file_buf cache_mng.c:381) [ino: 20028] Written [52482048:4096] bytes, result: OK
16:28:23 [fuse] (rfuse_write_cb rfuse.c:717) [req: 0x2e3c460] write_cb success: YES
16:28:23 [dir_tree] (dir_tree_on_buffer_written_cb dir_tree.c:1475) [ino: 20028, fop: 0x54d22b0] Buffer written, count: 4096
16:28:23 [fuse] (rfuse_write rfuse.c:732) [ino: 20029, fi: 0x7ffee81d5780] write inode, size: 4096, off: 23683072
16:28:23 [dir_t16:28:24 [main] (main main.c:877) Mountpoint /d1/s2s/s3/optimus does not exist! Please check directory permissions!
16:28:24 [main] (application_destroy main.c:508) Destroying application !
16:28:25 [main] (main main.c:877) Mountpoint /d1/s2s/s3/optimus does not exist! Please check directory permissions!
16:28:25 [main] (application_destroy main.c:508) Destroying application !
16:28:27 [main] (main main.c:877) Mountpoint /d1/s2s/s3/optimus does not exist! Please check directory permissions!
16:28:27 [main] (application_destroy main.c:508) Destroying application !
16:28:30 [main] (main main.c:877) Mountpoint /d1/s2s/s3/optimus does not exist! Please check directory permissions!
16:28:30 [main] (application_destroy main.c:508) Destroying application !

@wizzard
Copy link
Member

wizzard commented Dec 14, 2017

Hello,
without any additional logs I can't tell you for sure what happened.

This log says that for some reason "Mountpoint /d1/s2s/s3/optimus does not exist".
Could you please check if any other running script removes this mount or folder?

@crodwell
Copy link
Author

Hi, how could I get some additional logs? This verbose setting writes GB's to disk.

The mount point exists, it just gets tied up by RioFS somehow.
Once it's finally crashed, I cannot restart RioFS until I umount. However doing an umount too soon; gives this:
umount: /d1/s2s/s3/optimus: target is busy
(In some cases useful info about processes that
use the device is found by lsof(8) or fuser(1).)

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