AzureStorageExplorer
AzureStorageExplorer copied to clipboard
Export entities to a file is not working
Preflight Checklist
- [X] I have installed the latest version of Storage Explorer.
- [X] I have checked existing resources, including the troubleshooting guide and the release notes.
- [X] I have searched for similar issues.
Storage Explorer Version
1.24.2
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Linux (tar.gz)
OS Version
No response
Bug Description
{ "name": "Error", "message": "ENOSYS: function not implemented, write", "stack": "Error: ENOSYS: function not implemented, write", "errno": -38, "code": "ENOSYS", "syscall": "write" }
Steps to Reproduce
Try to export anything.
Actual Experience
When am trying to do an export query, it throws the above error.
Expected Experience
No response
Additional Context
No response
@sharmi-19 What distribution of Linux are you using and what version? Does this also happen if you try downloading a blob to the same location you are trying to save the export file?
Hi @craxal I have the same issue, with the same error details. I can dowload blobs, just the export from tables is not working. When i try to export, in the Activities screen i see something like this: "Failed to export entities from table 'TableName' to '/run/user/1000/doc/8d8e0514/TableName.csv' " I checked this csv file, and only the csv header line was filled without any data
Storage Exporer About: Version 1.24.3 AzCopy Version: 10.14.1
Platform: Linux Architectur: x64 Build Number: 20220617.2 Commit: 3ccc8329e Support ID: e86469b3-d13e-92ac-cbc8-071e9b19543f
-------------- Env --------------- $snap list storage-explorer Name Version Rev Tracking Publisher Notes storage-explorer 1.24.3 38 latest/stable msft-storage-tools✓ -
$lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal
$uname -a Linux ********* 5.13.0-51-lowlatency #58~20.04.1-Ubuntu SMP PREEMPT Tue Jun 14 12:26:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
@sharmi-19 @pintmil Does the error have any more details you can share (is there a "Details..." action you can click on)?
@sharmri-19 @pintmil Does the error have any more details you can share (is there a "Details..." action you can click on)?
No after i click to the export button and select the "Export selected" options, in the activities screen i see that something happenin, but after 1 second it fails with the "Failed to export..." error message. After i click on it, it shows the error detail window, with this message:
{
"name": "Error",
"message": "ENOSYS: function not implemented, write",
"stack": "Error: ENOSYS: function not implemented, write",
"errno": -38,
"code": "ENOSYS",
"syscall": "write"
}
I checked the logs, maybe it can help:
[2022-06-30T10:43:06.648Z] (ActivityProvider:35202) <INFO> Activity added {
title: "Queued export from table 'Obu' to '/run/user/1000/doc/18bebdb0/Obu.csv'",
message: '',
speed: undefined,
progress: undefined,
status: 0,
actions: []
}
[2022-06-30T10:43:06.813Z] (main:34798) <INFO> Launched Node process 35214 for provider 'JobQueueProvider'
[2022-06-30T10:43:06.793Z] (JobQueueProvider:35214) <NONE> Log file: /home/mil/snap/storage-explorer/38/.config/StorageExplorer/logs/2022-06-30_124239/2022-06-30_124239_JobQueueProvider_35214.log
[2022-06-30T10:43:06.795Z] (JobQueueProvider:35214) <NONE> Log level: info
[2022-06-30T10:43:06.811Z] (JobQueueProvider:35214) <INFO> Loading SSL Settings
[2022-06-30T10:43:06.811Z] (JobQueueProvider:35214) <INFO> Injecting certs found in /home/mil/snap/storage-explorer/38/.config/StorageExplorer/certs/
[2022-06-30T10:43:06.812Z] (JobQueueProvider:35214) <INFO> Sending init acks back to parent process
[2022-06-30T10:43:07.344Z] (main:34798) <INFO> Launched Node process 35227 for provider 'JobHandlerProvider'
[2022-06-30T10:43:07.324Z] (JobHandlerProvider:35227) <NONE> Log file: /home/mil/snap/storage-explorer/38/.config/StorageExplorer/logs/2022-06-30_124239/2022-06-30_124239_JobHandlerProvider_35227.log
[2022-06-30T10:43:07.326Z] (JobHandlerProvider:35227) <NONE> Log level: info
[2022-06-30T10:43:07.343Z] (JobHandlerProvider:35227) <INFO> Loading SSL Settings
[2022-06-30T10:43:07.343Z] (JobHandlerProvider:35227) <INFO> Injecting certs found in /home/mil/snap/storage-explorer/38/.config/StorageExplorer/certs/
[2022-06-30T10:43:07.344Z] (JobHandlerProvider:35227) <INFO> Sending init acks back to parent process
[2022-06-30T10:43:07.699Z] (ActivityProvider:35202) <INFO> Activity finalized {
title: "Failed to export entities from table 'Obu' to '/run/user/1000/doc/18bebdb0/Obu.csv'",
message: '',
speed: undefined,
progress: undefined,
status: 3,
actions: [ 'View Errors' ]
}
@pintmil This is an error message I've seen before, though I haven't been able to narrow down of the cause as of yet. Are you using the .tar.gz or the snap? What location are you trying to save the export file to? Does the export succeed if you save somewhere within your user home directory?
@craxal I installed the StorageExplorer from snap. I tried to save the export csv file into different folders, to my home directory too, but the same error happend in every case.
@pintmil Interesting. Based on some of my searching, it's possible this may be a hardware issue. What kind of hardware are you running Ubuntu on? Also, what file system format is your system using?
@pintmil any response to @craxal 's question? Your bug is interesting to say the least.
@craxal @MRayermannMSFT sorry i was on holiday. I use the software on a HP Zbook g4 laptop my linux partition is on a nvme ssd with xfs filesystem, nothing special. Everything else of my softwares work fine. Also i can save the blobs with the AzureStorageExplorer, just the csv export fails.
@pintmil The only difference I can think of between blobs and tables as far as file system access is concerned is Blobs uses AzCopy, whereas Tables uses Node's fs module. Can you upload or download .csv blobs? Have you tried the .tar.gz distribution to see if it has the same problem?
Closing due to lack of response. If you are still encountering this issue, we recommend opening a support ticket via the Azure Portal. Alternatively you can open a new issue here.