Search found 10 matches

by pvanbeek
Fri Mar 30, 2018 5:21 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

Well, it turns out another drive was on the edge of failure. I removed that drive from the pool and the LZ is clearing now.

Thank you for the assistance in troubleshooting - this one can be marked as closed.

Phil
by pvanbeek
Thu Mar 29, 2018 6:15 pm
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

I tried that too, the same file and a new file in a "test folder". Something wonky is going on.

Phil
by pvanbeek
Thu Mar 29, 2018 8:36 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

I updated and rebooted - no luck.

Still getting the same error and the file is not clearing/moving from the LZ.

Phil
by pvanbeek
Wed Mar 28, 2018 6:01 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

I removed the "bad" drives from the storage pool (used greyhole --going=/path/to/storage/pool/drive) and the system automatically triggered an FSCK. Once that was completed, I tried to copy a small file over to test it. Here are the messages I am now receiving... https://paste.fedoraproject.org/past...
by pvanbeek
Tue Jan 23, 2018 12:19 pm
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

Permissions look good. I also stopped and restarted greyhole and then am in the middle of a greyhole --fsck. Looks like some bad news in there... I am seeing all sorts of warnings with respect to hdd3 and hdd4. They appear to be offline or have failed completely. That said, GH should find open space...
by pvanbeek
Tue Jan 23, 2018 11:28 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

Yes and no - the folder exists, but I changed the name in the original fpaste for privacy (apologies for any confusion). We just create new folders within the share from Windows machines, as needed, and copy files into the new directory, so my assumption is that GH is establishing the proper permiss...
by pvanbeek
Tue Jan 23, 2018 10:43 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

apaste returned a JSON error, so I used fpaste.

https://paste.fedoraproject.org/paste/H ... pkE60qQXsQ

Thank you again,
Phil
by pvanbeek
Mon Jan 22, 2018 10:47 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

Re: DEBUG & WARN Rename - failed to open stream

I configured it manually a few years back and it has been working since install. Sorry for the lack of attachment - new to fpaste, but I think this is the link:

https://paste.fedoraproject.org/paste/M ... lpx-~3a5XQ

Phil
by pvanbeek
Mon Jan 22, 2018 8:01 am
Forum: Storage Pooling/Greyhole
Topic: SOLVED: DEBUG & WARN Rename - failed to open stream
Replies: 16
Views: 1661

SOLVED: DEBUG & WARN Rename - failed to open stream

When trying to copy a file onto my server last night, I received an "insufficient space" error. Upon further inspection, I discovered that my LZ is full - appears the files are not moving to the proper GH storage location. I haven't changed my configuration, so not sure what is going on. Any help is...
by pvanbeek
Tue Feb 28, 2017 4:18 pm
Forum: VPN
Topic: CLOSED: OpenVPN main cert has expired - are there updated ones available?
Replies: 22
Views: 2443

Re: CLOSED: OpenVPN main cert has expired - are there updated ones available?

Confirmed that an uninstall/reinstall of the OpenVPN App solved things on the server side. I use HDAConnect on the client side. All that was needed was to copy the new certs over to the C:\Program Files (x86)\HDAConnect\config folder and then edit the config file to use the new certificate names. BI...