[k3b] [Bug 397732] K3B: data project: when burning wrong size of written data is displayed

[Leslie Zhai]

https://bugs.kde.org/show_bug.cgi?id=397732

--- Comment #3 from Leslie Zhai <zhaixiang at loongson.cn> ---
(In reply to Thomas Schmitt from comment #2)
> Hi,
> 
> @Leslie:
> 
> I am the backend guy. Operating K3B is not really my turf and my K3B is old.
> (But i just pulled the freshest code from git.)

You are always my teacher :)

> 
> @Armin Mohring:
> 
> As far as i can see, the numbers for the progress messages stem from
> the writer modules k3bgrowisofswriter.cpp or k3bcdrecordwriter.cpp.

$ git log k3bgrowisofswriter.cpp or k3bcdrecordwriter.cpp

You lead me to fix BUG380064, BUG367639, BUG137436 and BUG372094.

> (Like "emit processedSize(...);".
> They seem to take their numbers from message output of the respective
> programs growisofs or cdrecord (or wodim).
> 
> When a burn run with my K3B has ended, then the window with the progress
> bar offers a button "Show Debugging Output" (at the lower right).
> There i can see the pacifier messages from growisofs.
> 
> In my try (with DVD+RW) the progress bar waited at 93 % until the medium
> was ejected. Then it hopped to 100 %. But the text still says
>   "755.0 MiB of 805.0 MiB"
> 
> This is halfways plausible from the view of K3B by the last pacifier
> message of growisofs:
> 
>   807534592/859508736 (94.0%) @4.0x, remaining 0:09 RBU 100.0% UBU  99.7%
> 
> growisofs reports to have written 807534592 of 859508736 bytes
> and to consider this as 94.0 percent of the job.
> 
> The "94 %" is very near to the "93 %" which i remember to have seen.
> 807534592/859508736 = .939530406355288. So it is plausible to see 93.
> But 807534592 bytes = 770.125 MiB. 859508736 bytes = 819.69140625 MiB.
> So why 755.0 and 805 ? (xorriso too says its 859508736 bytes.)
> 
> No further message is recorded from growisofs. That's strange.
> 
> A direct run of growisofs (with an ISO image of similar size) ends by 
>     805109760/858783744 (93.8%) @4.0x, remaining 0:09 RBU 100.0% UBU  99.7%
>     823623680/858783744 (95.9%) @4.0x, remaining 0:06 RBU 100.0% UBU  99.7%
>     842104832/858783744 (98.1%) @4.0x, remaining 0:03 RBU  49.7% UBU  99.7%

I need to find the root cause why K3B failed to receive the "full data volume",
for example 98.1%. And I need to build growisofs for mips64el manually.
https://mail.kde.org/pipermail/k3b/2018-August/002201.html

Hi Armin, please directly run growisofs in your environment to double check,
thanks!

>   builtin_dd: 419328*2KB out @ average 3.9x1352KBps
>   /dev/sr4: flushing cache
>   /dev/sr4: stopping de-icing
>   /dev/sr4: writing lead-out
> 
> In comparison, this looks as if K3B is not logging all messages from
> growisofs, possibly because it does not receive them all.
> The reasons for this would be out of my expertise.

It is my job :)

> 
> Have a nice day :)
> 
> Thomas

-- 
You are receiving this mail because:
You are the assignee for the bug.