Community

Subscribe
Highlighted

OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hello Community,

we rolled out OSSV on several Windows Servers and now the Windows Application Log reports the Following Error. ID "4102", Source "SnapVault".

D:\ <Destination Filer>:/vol/<Destination Volume>/Dxx Unexpected read select while no data pending

I found several Community Discussions regarding that but no solution overall.

The OSSV Install Log shows that we have the following Version is installed.

NetApp Host Agent version 2.7 (2.7.0.2203)

Agent Core Library version 2.7 (2.7.0.2203)

The destination filer runs the following Ontap version

NetApp Release 8.1.2P4 7-Mode:

Attached you'll find the latest logfile.

Want to ask if this is a configuration or known Problem and how to solve it?

Best Regards

Daniel

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Uncheck the box 'Run estimator before each backup' in the OSSV configurator and check if that helps.


Also, check the SnapMirror log for any error on the filer (/etc/log/snapmirror).

Thanks,

-Ashwin

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hoi Ashwin,

thanks a lot for your reply! Have unchecked the estimator and will have a look into the logs. Will let you know as soon as I have any news.

Best Regards


Daniel

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hoi Ashwin,


a big SORRY for late reply. Have unchecked the box 'Run estimator before each backup' in the OSSV configurazor and still get these messages.

E:\<Destination Filer>:/vol/ossv_v_lx_<Servername>/Exx Unexpected read select while no data pending

Had a look at the Snapmirror Log and have nearly at the same time the following message.

dst Fri Jun 14 03:48:12 CES <Server Name>:E:\ <Destination Filer>:/vol/ossv_v_lx_<Server Name>/Exx Abort (could not read from socket)

So, uncheck the box didn't solve the problem.

Thanks a lot for your help.

Best Regards

Daniel

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hi Daniel,

That's alright. No need to sorry . I guess, its a community and we are all busy and we hope there is always someone or the other to pitch in.

What is the snapvault settings on filer?
filer>options snapvault


Please send me this log file:

To collect, go to (for windows):

C:\Program Files\netapp\snapvault\bin>OSSVINFO.exe -s filer -l rootSmiley Tongueassword ossvinfo

'Ossvinfo' is saved in /bin directory in the same path.

Thanks,

-Ashwin

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hoi Ashwin,

thanks a lot for your answer.

Snapvault Stettings are:

> options snapvault

snapvault.access             all

snapvault.enable             on

snapvault.lockvault_log_volume

snapvault.nbu.archival_snap_default on

snapvault.ossv.compression   on

snapvault.preservesnap       off

snapvault.snapshot_for_dr_backup vsm_base_only

Please find the output of OSSVINFO attached. Thanks a lot.

Daniel

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hi Daniel,

I can't seem to find anything wrong with the ossv config file, but this error is indicating something to do with the "network", but I can't figure out what it might be. Lets try to isolate it further..

On the filer (for - snapvault.access) , remove 'all' and put the IP address instead as shown below, and run the backups again. (Note: if there are multiple ossv hosts, then comma seprated values are allowed.)

filer>options snapvault.access host=x.x.x.x

Also, try running packet trace, may be we can catch something.

filer> pktt start all -i x.x.x.x -d /etc/log
Note: ‘-i’  is the IP address of ossv host, and '-d' is used to save the files to the given directory.

Thanks,

-Ashwin

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Hoi Ashwin,

we have about 30 Hosts using Snapvault, is there any character limitation in options snapvault.access host ? Will it help to do the packet trace before removing the host? Or do you suggest to change first the option and then do the packet trace?

Best Regards


Daniel

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

I am not aware of any limitation as such.

But, lets take another route, before chaging the 'all' setting for snapvault host access, Add IP/hostname entry for OSSV host that is expereincing this issue on the filer's /etc/hosts file.

once added, entry would look something like this:

filer>rdfile /etc/hosts
x.x.x.x  ossvhostname

See if this helps.

Thanks,

-Ashwin

Re: OSSV reports "Unexpected read select while no data pending" for all Drives on Windows Server

Do any of these help?

https://support.quest.com/SolutionDetail.aspx?id=SOL81255

http://it.toolbox.com/blogs/borgblog/typical-work-day-19788

Have you checked that the VSS provider is fucntioning correctly? Can you create a shadow copy manually?

'vssadmin create shadow [path]'