Opened 12 years ago
Closed 8 years ago
#9787 closed bug (fixed)
NFS2: Very big values in Tracker and 'ls -sla'
Reported by: | jahaiku | Owned by: | mmu_man |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | File Systems/NFS | Version: | R1/Development |
Keywords: | Cc: | diger | |
Blocked By: | Blocking: | #10285 | |
Platform: | All |
Description
If I do a ls -lsa on the NFS2 even for empty files a very big value is shown in the first column. See in the attached screenshot. When copying via Tracker the progress is messed up with the same big values. This is gcc4 build of hrev45700.
The patch enables the commented line for the blocks of a file.
Instead of the line in the patch the following should work, too:
st->st_blocks=(st->st_size+st->st_blksize-1)/st->st_blksize;
I haven't tested it, because I'm not certain if this is correct for the error. Does someone know if this is correct for NFS2?
Attachments (4)
Change History (13)
by , 12 years ago
by , 12 years ago
Attachment: | nfs2_blocks.patch added |
---|
comment:1 by , 12 years ago
patch: | 0 → 1 |
---|
comment:2 by , 12 years ago
Cc: | added |
---|---|
Version: | R1/alpha4.1 → R1/Development |
comment:3 by , 12 years ago
comment:5 by , 11 years ago
png works now. almost all those files are anywhere between 4-30gig. certainly all the ones around 300MB should be in the gigabytes too.
comment:6 by , 11 years ago
Btw, I started work on a new filesystem-add-on for NFSv2/v3 a while ago. I cannot yet say when it will be finished, but it should then solve this issue as well.
comment:7 by , 11 years ago
Considering we have a working NFSv4 client, the need for v2 and 3 is much less pressing...
comment:8 by , 11 years ago
Well, my older NAS-unit unfortunately doesn't support NFSv4, so it's pretty much "scratching a personal itch" ;-)
I now had the time to build Haiku and test the patch. 'ls -lsa' and the status window in Tracker showing correct values with the patch.