I imported a zpool but can not access files.

[Luminus]

I exported then imported a zpool now I can not access the data on the system. The system shows space is being used but when I tried to create a share none of the files show even though I am mapping to the same dataset. (I use the web GUI).

 

[Samuel Tai]

When you exported, what options did you check?

When you imported, does the pool show up under Storage->Pools?

 

[Luminus]

When you exported, what options did you check?

When you imported, does the pool show up under Storage->Pools?

I pick the bottom two.

 

[Luminus]

When you exported, what options did you check?

When you imported, does the pool show up under Storage->Pools?

 

[Luminus]

Yes it does.

 

[Samuel Tai]

OK, so this is a permissions/ACL issue on your shares. Since you checked the "Delete configuration of shares", that destroyed the share definition in Sharing->Windows Shares.

Try resetting the dataset ACL back to defaults via setfacl -b /mnt/HouseofGivensZFS.

Also, you'll need to create a dataset underneath your root for sharing. It's not possible to share out the root dataset. Once you create the daughter dataset, you'll need to move your data into it via the Shell, using mv -R commands.

 

[Luminus]

OK, so this is a permissions/ACL issue on your shares. Since you checked the "Delete configuration of shares", that destroyed the share definition in Sharing->Windows Shares.

Try resetting the dataset ACL back to defaults via setfacl -b /mnt/HouseofGivensZFS.

Also, you'll need to create a dataset underneath your root for sharing. It's not possible to share out the root dataset. Once you create the daughter dataset, you'll need to move your data into it via the Shell, using mv -R coS

Would that look like "mv/mnt/HouseofGivensZFS mnt/HouseofGivensZFS/HouseofGivensZFS"? Thanks for all the help

 

[Samuel Tai]

Having a daughter dataset with the same name will make mv tricky to accomplish. If that's your taste, a CLI GUI option using mc may be better. You'll be able to select files for moving into the daughter dataset.

 

[Luminus]

Having a daughter dataset with the same name will make mv tricky to accomplish. If that's your taste, a CLI GUI option using mc may be better. You'll be able to select files for moving into the daughter dataset.

No worries. I can change the name no problem. Did I type the command correctly?

 

[Samuel Tai]

Did I type the command correctly?

Nope. Let's assume you named your daughter dataset foo. You'd need something like this:

cd /mnt/HouseofGivensZFS
find . \! -regex ".*/foo/.*" -exec mv {} ./foo

This traverses everything in the root dataset that doesn't match a path underneath foo, and then mvs it under foo.

 

[Luminus]

Nope. Let's assume you named your daughter dataset foo. You'd need something like this:

cd /mnt/HouseofGivensZFS
find . \! -regex ".*/foo/.*" -exec mv {} ./foo

This traverses everything in the root dataset that doesn't match a path underneath foo, and then mvs it under foo.

 

[Luminus]

I do not think I did it right.

 

[Samuel Tai]

My apologies, I left out the \; at the end of the exec.

cd /mnt/HouseofGivensZFS
find . \! -regex ".*/foo/.*" -exec mv {} ./foo \;

 

[Luminus]

My apologies, I left out the \; at the end of the exec.

cd /mnt/HouseofGivensZFS
find . \! -regex ".*/foo/.*" -exec mv {} ./foo \;

No worries. I really appreciate all the help. I am very much a rookie at this. Still not getting it right. Can you see where I am failing.

 

[Samuel Tai]

I'm curious about how you have your pool constructed. You seem to have structured things like this:

Code:

HouseofGivensZFS
  HouseofGivensZFS
  HoG
    HoG

What I think you should have is:

Code:

HouseofGivensZFS
  HoG <- all your data moves here

For example, here's how I have my pool structured:

Code:

main
  .bhyve
    1_rancher
  container-s3-vols
  hdhomerun
  home
    local
    windows
  media
  zvols
    rancher-zvol (this is a VOLUME)

I don't have any data at the top level; I only use it to host daughter datasets. Some daughters have grand-daughters, but I keep those to a minimum.

 

[Luminus]

I'm curious about how you have your pool constructed. You seem to have structured things like this:

Code:

HouseofGivensZFS
  HouseofGivensZFS
  HoG
    HoG

What I think you should have is:

Code:

HouseofGivensZFS
  HoG <- all your data moves here

For example, here's how I have my pool structured:

Code:

main
  .bhyve
    1_rancher
  container-s3-vols
  hdhomerun
  home
    local
    windows
  media
  zvols
    rancher-zvol (this is a VOLUME)

I don't have any data at the top level; I only use it to host daughter datasets. Some daughters have grand-daughters, but I keep those to a minimum.

I did as you said and everything seemed to have transferred transferred but then this occurred. Is there a way I can move the information from FOO to HOG? When I copied the command, I accidentally hit enter and FOO was created.

 

[Samuel Tai]

Since everything is now under foo, try

mv /mnt/HouseofGivensZFS/foo/* /mnt/HouseofGivens/HoG

Then you can rmdir /mnt/HouseofGivens/ZFS/foo