<div dir="ltr"><div>Hi Ishita<br><br></div><div>So the problem is:<br><ul><li>ndnfs-port creates a zero-length segment if the file size is exactly 8KB.</li><li>The "PyNDN client" cannot correctly handle a zero-length segment.<br></li></ul></div><div>I'm unsure which software is violating the protocol. A zero-length segment by itself is certainly not a protocol violation because it is the only way to represent an empty file, but I'm unsure about a zero-length segment at the end of a non-empty file.<br>I have CC'ed ndn-app, the support list of ndnfs-port. Let's see what the maintainer of ndnfs-port says about this problem.<br></div><div><br></div><div>In the meanwhile, can you provide a link to the "PyNDN client" you are using? I can't find an official PyNDN-based client for NDNFS protocol.<br></div><div><br></div>Yours, Junxiao<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 19, 2017 at 11:04 AM, Ishita Dasgupta <span dir="ltr"><<a href="mailto:ishita.dasgupta@gmail.com" target="_blank">ishita.dasgupta@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">Hi Junxiao, </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">You're right. I tested with a 30MB file and it worked. Somehow for the multiples of 8KB files, the last segment is set as 0. Is there any workaround that situation or is this a bug with ndnfs-port that has not been corrected yet? Can I just change the fixed segment size of 8 KB?</div><div class="gmail_extra"><br clear="all"><div><div class="m_2535641639596162498m_-6880241115454691203gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font face="tahoma, sans-serif"><span style="font-size:12.8000001907349px"><div class="gmail_default" style="font-family:tahoma,sans-serif;display:inline">Thanks,</div></span></font><br></div></div><div dir="ltr"><font face="tahoma, sans-serif"><span style="font-size:12.8000001907349px"><div class="gmail_default" style="font-family:tahoma,sans-serif;display:inline">Ishita</div></span></font></div></div></div></div></div></div><div><div class="h5">
<br><div class="gmail_quote">On Sat, Jul 15, 2017 at 3:08 PM, Junxiao Shi <span dir="ltr"><<a href="mailto:shijunxiao@email.arizona.edu" target="_blank">shijunxiao@email.arizona.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="auto">Hi Ishita</div><div dir="auto"><br></div><div dir="auto">I have successfully served 30MB files in my deployment.</div><div dir="auto"><br></div><div dir="auto">This might be a bug on segmentation, instead of a bug related to large file size. 1KB, 10KB, 100KB are not multiply of 8KB.</div><div dir="auto">If my hypothesis is true, you should see this problem with exact 8KB, 16KB, 24KB files; this problem should disappear if you add 1 byte after an 1MB or 100MB file.</div><div dir="auto">Can you try those sizes and report back?</div><div dir="auto"><br></div><div dir="auto">Yours, Junxiao</div><br><div class="gmail_quote"><div><div class="m_2535641639596162498m_-6880241115454691203h5"><div>On Sat, Jul 15, 2017 at 09:33 Ishita Dasgupta <<a href="mailto:ishita.dasgupta@gmail.com" target="_blank">ishita.dasgupta@gmail.com</a>> wrote:<br></div></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_2535641639596162498m_-6880241115454691203h5"><div><div class="gmail_default" style="font-family:tahoma,sans-serif">Hi All, </div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">I am trying to study performance of file download over ndn across different file sizes. </div><div class="gmail_default" style="font-family:tahoma,sans-serif">I am using ndnfs-port server to do the same, but I am receiving weird anomaly for file sizes > 1 MB. </div><div class="gmail_default"><font face="tahoma, sans-serif">It works fine for file sizes of 1KB,10KB and 100KB, but when it comes to 1MB or greater, the </font>ndnfs<font face="tahoma, sans-serif"> server application gives the following debug log for the last segment for each of these files </font></div><div class="gmail_default"><font face="tahoma, sans-serif"><br></font></div><div class="gmail_default">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font size="1"><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1">- 1500131726 DEBUG: sign_segment: path=/1MB.txt, ver=1500131708, seg=127, len=8192<br></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1">- 1500131726 DEBUG: sign_segment: segment name is /ndn/broadcast/ndnfs/1MB.txt/%<wbr>FDYj1%7C/%00%7F<br></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1">- 1500131726 DEBUG: sign_segment: path=/1MB.txt, ver=1500131708, seg=128, len=0<br></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1">- 1500131726 DEBUG: sign_segment: segment name is /ndn/broadcast/ndnfs/1MB.txt/%<wbr>FDYj1%7C/%00%80</span></font></blockquote><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="background-color:rgb(255,255,255)"><font size="1"><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1"><font color="#000000" face="arial, helvetica, sans-serif">- 1499891047 DEBUG: sign_segment: path=/10MB.txt, ver=1499890866, seg=1279, len=8192<br></font></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1"><font color="#000000" face="arial, helvetica, sans-serif">- 1499891047 DEBUG: sign_segment: segment name is /ndn/broadcast/ndnfs/10MB.txt/<wbr>%FDYf%84%B2/%00%04%FF<br></font></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1"><font color="#000000" face="arial, helvetica, sans-serif">- 1499891047 DEBUG: sign_segment: path=/10MB.txt, ver=1499890866, seg=1280, len=0<br></font></span><font color="#000000" face="arial, helvetica, sans-serif"><span style="font-variant-ligatures:no-common-ligatures">- 1499891047 DEBUG: sign_segment: segment name is /ndn/broadcast/ndnfs/10MB.txt/<wbr>%FDYf%84%B2/%00%05%00</span> </font></font></span></blockquote><div><br></div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><font style="background-color:rgb(255,255,255)" color="#000000"><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1"><font size="1" face="arial, helvetica, sans-serif">- 1499893665 DEBUG: sign_segment: path=/100MB.txt, ver=1499892176, seg=12799, len=8192<br></font></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1"><font size="1" face="arial, helvetica, sans-serif">- 1499893665 DEBUG: sign_segment: segment name is /ndn/broadcast/ndnfs/100MB.txt<wbr>/%FDYf%89%D0/%001%FF<br></font></span><span class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail-s1"><font size="1" face="arial, helvetica, sans-serif">- 1499893665 DEBUG: sign_segment: path=/100MB.txt, ver=1499892176, seg=12800, len=0<br></font></span><font size="1" face="arial, helvetica, sans-serif"><span style="font-variant-ligatures:no-common-ligatures">- 1499893665 DEBUG: sign_segment: segment name is /ndn/broadcast/ndnfs/100MB.txt<wbr>/%FDYf%89%D0/%002%00</span> </font></font></blockquote>
</div><div class="gmail_default"><font style="background-color:rgb(255,255,255)" color="#000000" size="1" face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font style="background-color:rgb(255,255,255)" color="#000000" size="1" face="tahoma, sans-serif"><br></font></div><div class="gmail_default"><font face="tahoma, sans-serif"><span style="background-color:rgb(255,255,255)"><font size="1">T</font></span>his further causes </font><span style="background-color:transparent;white-space:pre-wrap"><font color="#cc0000" face="tahoma, sans-serif"><i>“File empty” for the last data packet when using PyNDN client</i></font></span><font face="tahoma, sans-serif"><i><font color="#cc0000">.</font></i><font color="rgba(0, 0, 0, 0)"> </font><font color="#000000">The client works fine as long as the last segment (data packet) size on the server is not 0. </font></font></div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">Does anyone have any clue as to why this might be happening? Could this be a problem with the files itself? I know ndnfs-port fixes file segment sizes to 8KB, but I couldn't find any explanation that would suggest that it has a size limit when it comes to file download.</div><div><div class="m_2535641639596162498m_-6880241115454691203m_5153166337964205196m_-3629553672371713666gmail_signature"><div><div><div></div></div></div></div></div>
</div></div></div>
______________________________<wbr>_________________<br>
Ndn-interest mailing list<br>
<a href="mailto:Ndn-interest@lists.cs.ucla.edu" target="_blank">Ndn-interest@lists.cs.ucla.edu</a><br>
<a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest" rel="noreferrer" target="_blank">http://www.lists.cs.ucla.edu/m<wbr>ailman/listinfo/ndn-interest</a><br>
</blockquote></div></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>