Cannot delete malformed iSCSI extent

[Arun Gupta]

When creating iSCSI file extent, I specified only directory name but forgot the filename. FreeNAS gave me a warning that filename is required. I realized my mistake and pressed Cancel.

However, FreeNAS still created the extent and now I cannot delete this extent. When I click on the extent, I get a long report. I am posting just the report header. Because of this bad extent, I cannot create any new extent and I cannot view the existing extents. I can access only the existing extents. How do I delete this malformed extent?

Thanks...

Request Method: GET
Request URL: http://xxx.xxx.xxx.xxx/admin/services/iscsitargetextent/edit/19/
Software Version: FreeNAS-9.2.0-RELEASE-x64 (ab098f4)
Exception Type: TypeError
Exception Value:
'NoneType' object has no attribute '__getitem__'
Exception Location: /usr/local/www/freenasUI/../freenasUI/services/forms.py in __init__, line 1173
Server time: Sat, 28 Dec 2013 12:55:55 -0500

 

[dlavigne]

Please create a report at bugs.freenas.org that contains the contents of the traceback and post the issue number here.

 

[Arun Gupta]

Thanks. My data is totally non-critical and I have already got yelled at by cyberjock, one of the forums admin, for posting question about non-critical data. If FreeNAS has a bug, so be it. I will find something else to work with.

Thanks...
Arun

 

[cyberjock]

I didn't "yell" at you for posting questions about non-critical data. I "yelled"(if you even want to call it that) because you sat there and asked a question about how to upgrade your pool while simultaneously using a striped pool AND telling me the data isn't important. Go read my response.

Either your data is important(and you are making a big mistake using a striped pool) or your data isn't important(and you should simply delete the pool and recreate it with the new disks). What I don't appreciate is people that are going to lie to me/themselves while simultaneously not listening to their own responses. Striped pools will fail suddenly and without warning. So there's no difference between deleting your pool now and zfs failing you suddenly later. Don't like the reality then don't do striped pools!