FreeNAS-9.3-STABLE-201602031011; hardware as in my sig.
I exported one of my pools, but when I try to import it again I get an error message: "File name too long" concerning a directory.
Although it will not import, it is mounted, and from the command line I can cd to the root of the unimportable pool, rm the files under that directory and rmdir the directory, but when I reboot and try to reimport the pool again, I get the same error message:
When I look, I see that the too-long directory path has been recreated but is empty.
Is there any way to reimport this pool? And is this not evidence of a bug in FreeNAS -- that it allows creation of file/path names that cannot be imported?
I exported one of my pools, but when I try to import it again I get an error message: "File name too long" concerning a directory.
Although it will not import, it is mounted, and from the command line I can cd to the root of the unimportable pool, rm the files under that directory and rmdir the directory, but when I reboot and try to reimport the pool again, I get the same error message:
Code:
Mar 10 11:56:27 freenas manage.py: [middleware.notifier:3517] Importing Backup_Pool [9569454016000112987] failed with: cannot mount 'Backup_Pool/Pool1_New_Backup/.warden-template-portjail-9.2-RELEASE-x64-20140219201213': File name too long Mar 10 11:56:27 freenas manage.py: [middleware.exceptions:37] [MiddlewareError: The volume "Backup_Pool" failed to import, for futher details check pool status]
When I look, I see that the too-long directory path has been recreated but is empty.
Is there any way to reimport this pool? And is this not evidence of a bug in FreeNAS -- that it allows creation of file/path names that cannot be imported?