SOLVED Can't find right path to fix 100% full NAS

Status
Not open for further replies.

mmm91492

Cadet
Joined
Nov 20, 2014
Messages
2
Hello everyone,

We have a NAS in our office that we send encrypted StorageCraft backups to, and while they were previously set to delete old backups, this setting was overwritten and our NAS quickly filled up.

I've read through this thread (https://forums.freenas.org/index.php?threads/disk-full-cant-delete-any-files-please-help.12252/) and I'm really hoping I can free up some space using the echo > command in the shell. The problem is that I can't find the right path to use, everything I try is returning "no such file or directory."

The network path is \\NAS\Backup\Addy\C_VOL-b0005.spf, but I'm having trouble translating this into the related path on the NAS. I have 0 experience operating a NAS, but I accessed the GUI and I'm pretty certain my ZFS Pool is named "RAID". "RAID" seems to contain "raidz1-0", which in turn contains "ada0p2" through "ada3p2".

Am I correct in assuming "RAID" is the pool? I would expect the necessary command to be "echo > /mnt/RAID/Backup/Addy/C_VOL-b005.spf", but again I get the error "no such file or directory exists." I've tried several different variations, but can never seem to find a file.

I'd really like to find a way to make this solution work as it sounds like the only other alternative is wiping the whole pool and starting fresh. I have copies of the most recent backups, so this wouldn't be out of the question, I'd just prefer a quicker, easier solution if possible.

Thanks for helping me out!
 

mmm91492

Cadet
Joined
Nov 20, 2014
Messages
2
Solved, turns out the right path was /mnt/RAID/Addy/C_VOL-b0005.spf.

I'll definitely keep an eye on my free space from now on...
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
Just some info for you...

9.2.1.x warns you of a pool gets above 80%, then again at 95%. You should be getting emails every day you are above 80%. If you aren't you haven't setup emailing. Not setting up emailing is bad because that *is* the primary communication from your server to you when things go wrong. As you've witnessed firsthand, not having that communication channel can be a mess. You are lucky in that your problem was recoverable. But there are many in this forum that have had unrecoverable problems (and total data loss) because they didn't setup emails.
 

depasseg

FreeNAS Replicant
Joined
Sep 16, 2014
Messages
2,874
Status
Not open for further replies.
Top