Lurkr
Dabbler
- Joined
- Mar 16, 2017
- Messages
- 20
TL;DR:
- I dun f*#@d up, lol
- Use an entire drive (ada0) as a swap memory space temporarily
- Mount said swap across reboots temporarily
- Import pool without panics/reboots.
- un-dedup data
- export
- reinstall freeNAS, and rebuild OS-side.
- I am open to ideas
- Thank you all in advance.
Intro:
Hello, I've been using FreeNAS since about 2012, but without being successful in any repair attempts I hadn't posted on here until now.
Random tidbits:
I'll spare the deets as to why I even thought to deduplicate the thing until the second post on this thread, if anyone is interested. Likewise what I've already tried. I've searched for hours on google and here for tidbits of information I could combine to result in my end goal to little avail.
I've tried adding system tunables "swapfile=/dev/ada0p1", "swapfile=/dev/ada0", editing fstab, editing rc.conf, etc.
Hopefully (and forgive my train of thought) I will be able to make this into a guide for those with kernels which panic upon importing a pool with oversized/broken dedup/arc tables (applicable to anyone who didn't follow Cyberjock's constant reminder to use more than 5GB/TB).
Problem:
I had a pool running, with some dedup datasets, which I then tried to un-dedup (create new dataset with compression, mv command from Putty, delete original deduped dataset), and then things went wrong, and a plethora of wrong turns, and hardware limitations, bring me to the conclusion that I need way more than 16GB Ram to import the 6x3TB z1 array properly.
Proposed Solution:
Adding swap is my proposed solution, and forgive me on how 'insecure' my idea is, its not to be a permanent fix, just a data recovery hackjob solution. Adding the 40GB drive in to the previously unused IDE channel.
Main Hangup:
I think that adding a tunable "swapfile" valued "/dev/ada0" of type "RC" is on the right track, but having it actually use it (showing up in swapinfo command) seems to be the difficulty.
FreeNAS:
FreeNAS-9.10.2-U2 (e1497f2)
Hardware:
Motherboard: Asus TurboV Evo
CPU: AMD Athlon II x4 635
RAM: 16352 MB
Boot: 2x Lexar 8GB mirrored
HDD (Data): 6 * 3TB (WD or Seagate, can't remember) in a RaidZ1 config (each drive has 50 GB reserved for swap)
HDD (temporary swap drive): 40GB IDE ada0
HDD Controller: (onboard)
NICs: Onboard, and Dell Gb/s card.
I also have assorted old low-sized drives available to use if need be. I do NOT have more RAM, I do have better boards with better processors, and more SATA ports though.
- I dun f*#@d up, lol
- Use an entire drive (ada0) as a swap memory space temporarily
- Mount said swap across reboots temporarily
- Import pool without panics/reboots.
- un-dedup data
- export
- reinstall freeNAS, and rebuild OS-side.
- I am open to ideas
- Thank you all in advance.
Intro:
Hello, I've been using FreeNAS since about 2012, but without being successful in any repair attempts I hadn't posted on here until now.
Random tidbits:
I'll spare the deets as to why I even thought to deduplicate the thing until the second post on this thread, if anyone is interested. Likewise what I've already tried. I've searched for hours on google and here for tidbits of information I could combine to result in my end goal to little avail.
I've tried adding system tunables "swapfile=/dev/ada0p1", "swapfile=/dev/ada0", editing fstab, editing rc.conf, etc.
Hopefully (and forgive my train of thought) I will be able to make this into a guide for those with kernels which panic upon importing a pool with oversized/broken dedup/arc tables (applicable to anyone who didn't follow Cyberjock's constant reminder to use more than 5GB/TB).
Problem:
I had a pool running, with some dedup datasets, which I then tried to un-dedup (create new dataset with compression, mv command from Putty, delete original deduped dataset), and then things went wrong, and a plethora of wrong turns, and hardware limitations, bring me to the conclusion that I need way more than 16GB Ram to import the 6x3TB z1 array properly.
Proposed Solution:
Adding swap is my proposed solution, and forgive me on how 'insecure' my idea is, its not to be a permanent fix, just a data recovery hackjob solution. Adding the 40GB drive in to the previously unused IDE channel.
Main Hangup:
I think that adding a tunable "swapfile" valued "/dev/ada0" of type "RC" is on the right track, but having it actually use it (showing up in swapinfo command) seems to be the difficulty.
FreeNAS:
FreeNAS-9.10.2-U2 (e1497f2)
Hardware:
Motherboard: Asus TurboV Evo
CPU: AMD Athlon II x4 635
RAM: 16352 MB
Boot: 2x Lexar 8GB mirrored
HDD (Data): 6 * 3TB (WD or Seagate, can't remember) in a RaidZ1 config (each drive has 50 GB reserved for swap)
HDD (temporary swap drive): 40GB IDE ada0
HDD Controller: (onboard)
NICs: Onboard, and Dell Gb/s card.
I also have assorted old low-sized drives available to use if need be. I do NOT have more RAM, I do have better boards with better processors, and more SATA ports though.