Moved zfs dataset, now CIFS is balking

[UnaClocker]

So I moved this dataset at the command line, using something like:
zfs set mountpoint=/Downloads raidA/Downloads
(for some reason it forces the leading /mnt part, but anyways..) Now the GUI is refusing to acknowledge it's existence when I go to share it. Is there some way to move this in the GUI that will make it happy? How do I get around this problem?

 

[SweetAndLow]

If you do something on the command line the gui has no clue what you did. If you want to use the CLI you need to use just normal FreeBSD and not freenas. Freenas expects you to use the GUI as much as possible.

It is also quite strange that you have bin,boot,dev,etc under your /mnt directory. That is not normal and you have messed something up that is causing lots for problems.


Also all posts need to follow the rules, So providing your hardware and Freenas version is required.

 

[UnaClocker]

Not sure how my hardware matters. FreeNAS is pretty much the latest version (FreeNAS-9.3-STABLE-201601181840), downloading the latest update now. Providing my hardware would just lead to more criticism about how I've chosen the wrong components or other feedback I don't want/need.
How can I change the mount location of a dataset from the GUI? I'm happy to use the GUI if it's possible to do the things I want to do.

 

[SweetAndLow]

You don't change the mount location. You shouldn't ever have a reason to do that. As it stands now you are trying to mount to the root of your boots device. This is a poor choice because you want you data to be separated from your boot device. So when your boot device dies you don't have issues with your data also.

Freenas is an appliance and expects things to be a certain way. This is how it can simplify things for the user. If you want to do non standard things you are better off with a freebsd install.

Why exactly do you want to change the mount point? I bet we can come up with a better solution.

 

[jde]

Your hardware choices are important in trying to help you find a way out of the mess you are in. For instance, if you've only got 1 TB of data, a forum member might suggest simply copying your data off of freenas, reinstall, and copy back. However, if you've got dozens of TB of data, that is a less attractive option.

Also, remember that you catch more flies with honey than with vinegar. You registered with this forum to get help from others, for free, to dig you out of the hole you are in. You are likely to get more help if you follow the rules and post your system specs.

You might check this thread to see if it's helpful to your problem.
https://forums.freenas.org/index.php?threads/cannot-mount-one-dataset-to-another.40932/

 

[UnaClocker]

I was thinking it'd be nice to have all of my media files, say music, tv shows, movies under /media. I wanted my Downloads folder under /mnt, rather than /mnt/raidA/Downloads But I guess that's really just for convenience when I'm moving files around at the command line. Less typing, easier to remember where things are.
I agree that my "zroot" pool is a bit messy. I had previously had a full FreeBSD install, and imported that pool when I installed FreeNAS, so I imagine that's why it has all the odd directories. I'm working on moving my data off that pool right now, then I will destroy that pool and start it over fresh.
And I updated my signature with my system details, per the rules.

 

[SweetAndLow]

And I updated my signature with my system details, per the rules.

Note: the rules say nothing about putting your hardware in your signature. Signatures don't show up when using any kind of mobile device so they are kind of worthless.

 

[UnaClocker]

*bangs head against desk* God I remember why I hate forums.

 

[jde]

I'm working on moving my data off that pool right now, then I will destroy that pool and start it over fresh.

Sounds like a good plan.

 

[UnaClocker]

Went well, it balked about me destroying that dataset, so I just shut down, removed the drives, brought it back up. It was somehow still in the list, but now it was happy to let me remove it. Tossed the two drives into my hackintosh so I could reformat them. Then back into the server and I created a new pool for them. I've noticed I can do a snapshot, then a zfs send/receive to move a dataset from one pool to another and the GUI doesn't freak out about it. So that's a nice plus.

 

[pirateghost]

Why are you running 3 different pools? Isn't that a pain in the ass to manage? Wouldn't you benefit from adding your vdevs to one pool and subsequently your data would be easier to manage?

 

[UnaClocker]

I chose this route because when I want to grow a pool, I don't have to replace 10 drives before I see the benefit.

 

[pirateghost]

I chose this route because when I want to grow a pool, I don't have to replace 10 drives before I see the benefit.

but you can add VDEVs to a pool. you don't have to replace 10 drives...

 

[UnaClocker]

But I don't want to add more, I want to replace the older smaller drives as the prices come down on the bigger ones. I've already got 10 drives in this machine. You want me to end up with 30 or something?

 

[pirateghost]

But I don't want to add more, I want to replace the older smaller drives as the prices come down on the bigger ones. I've already got 10 drives in this machine. You want me to end up with 30 or something?

This doesn't make sense....

you can have a SINGLE pool, with multiple VDEVs. Want to replace the drives? Replace them one at a time in individual VDEVs...once all drives in that VDEV are replaced, the pool size increases.

unless you don't plan on having 10 drives in your server forever? I don't get it.

 

[UnaClocker]

I don't get it either. And it's really not the problem I came here looking to solve.

 

[pirateghost]

I don't get it either. And it's really not the problem I came here looking to solve.

You know, it was a question of why you chose the path you did. No need to act that way. The defensiveness you have displayed in this thread is interesting.

 

[Mirfster]

So just to get it straight, it appears as if this is a recently new endeavor into FreeNas for you. At the very least, I would recommend taking the time to get yourself acquainted with the documentation (Manual, all the great posts/threads in these forums, etc..) before deciding to jump in with both feet. Heck, sign up for a free "Intro to FreeNAS (60-90 minutes)" online class while you are at it.

Learn to do things the right way, especially if you are going to go making YouTube videos about it. Last thing anyone in this community cares for is bad instructions/demonstrations being propagated.

You opened this thread on Feb 2nd stating:

So I moved this dataset at the command line

However, in your YouTube video (posted Jan 15th), within the first 20 seconds of the video you acknowledge that FreeNas does not like it when things are done via the CLI. Yet, you continued to do further configurations via CLI later?

In a later YouTube video (posted Jan 31st), you are trying to demonstrate how to upgrade drives by manually disconnecting them while the system is running (in what appears to be a system that does NOT have hot swap capabilities)? Then go on further to run a scrub to induce the error within the GUI? This is NOT the recommended method to replace/upgrade drives (especially on a mirror). If you spent any actual time on these forums (or read the Manual) you would understand the recommended way to not only replace drives, but to identify them as well (Hint, it has to do with the Serial Number).

Sorry, if this seems rude but the reality is that everyone here is willing to help. While the advice may not always come wrapped in roses, it is still the BEST place to get the CORRECT information.

Please, please, pretty please take some time to get a better understanding not only for the safety of your data but so you are not providing misinformation to others or even end up on the "How To Fail ... a guide to things not-to-do" thread...

 

[anodos]

So just to get it straight, it appears as if this is a recently new endeavor into FreeNas for you. At the very least, I would recommend taking the time to get yourself acquainted with the documentation (Manual, all the great posts/threads in these forums, etc..) before deciding to jump in with both feet. Heck, sign up for a free "Intro to FreeNAS (60-90 minutes)" online class while you are at it.

Learn to do things the right way, especially if you are going to go making YouTube videos about it. Last thing anyone in this community cares for is bad instructions/demonstrations being propagated.

You joined opened this thread on Feb 2nd stating:


However, in your YouTube video (posted Jan 15th), within the first 20 seconds of the video you acknowledge that FreeNas does not like it when things are done via the CLI. Yet, you continued to do further configurations via CLI later?

In a later YouTube video (posted Jan 31st), you are trying to demonstrate how to upgrade drives by manually disconnecting them while the system is running (in what appears to be a system that does NOT have hot swap capabilities)? Then go on further to run a scrub to induce the error within the GUI? This is NOT the recommended method to replace/upgrade drives (especially on a mirror). If you spent any actual time on these forums (or read the Manual) you would understand the recommended way to not only replace drives, but to identify them as well (Hint, it has to do with the Serial Number).

Sorry, if this seems rude but the reality is that everyone here is willing to help. While the advice may not always come wrapped in roses, it is still the BEST place to get the CORRECT information.

Please, please, pretty please take some time to get a better understanding not only for the safety of your data but so you are not providing misinformation to others or even end up on the "How To Fail ... a guide to things not-to-do" thread...

I like 1:50 here: https://www.youtube.com/watch?v=AIFTexC5xsU

You know, if you used a proper server motherboard you wouldn't need to do things like use a screwdriver to scratch up your HBA to get it to boot. :D

 

[Mirfster]

Yeah, noticed that as well (among other things); but didn't want to get too critical. :) Hopefully the OP continues on their FreeNas quest and helps to spread the correct information. As to whether or not this makes it to the "How To Fail ... a guide to things not-to-do" thread; that is another story...