How to know the progress of sfill free space wiping process?












3















I want to wipe free space in my ubuntu partition and after a search found this sfill software which I installed using




sudo apt install secure-delete




Then I have used this command to wipe free space



$ sudo sfill -v /home
[sudo] password for shan:
Using /dev/urandom for random input.
Wipe mode is secure (38 special passes)
Wiping now ...
Creating /home/oooooooo.ooo ...


its stuck here for last 20 minutes and I don't know whether sfill is working or not. In my /home partion oooooooo.ooo file has a size of 27.6 MB and stays in this size. How to know the progress of wiping of free space in sfill?










share|improve this question

























  • There are many ways to show progress , see stackoverflow.com/questions/238073/…

    – Panther
    Oct 3 '17 at 15:50











  • @bodhi.zazen, Yes, but do these work with sfill or zerofree?

    – sudodus
    Oct 3 '17 at 17:07











  • Possible duplicate of How to show the transfer progress and speed when copying files with cp?

    – karel
    Apr 10 '18 at 9:11
















3















I want to wipe free space in my ubuntu partition and after a search found this sfill software which I installed using




sudo apt install secure-delete




Then I have used this command to wipe free space



$ sudo sfill -v /home
[sudo] password for shan:
Using /dev/urandom for random input.
Wipe mode is secure (38 special passes)
Wiping now ...
Creating /home/oooooooo.ooo ...


its stuck here for last 20 minutes and I don't know whether sfill is working or not. In my /home partion oooooooo.ooo file has a size of 27.6 MB and stays in this size. How to know the progress of wiping of free space in sfill?










share|improve this question

























  • There are many ways to show progress , see stackoverflow.com/questions/238073/…

    – Panther
    Oct 3 '17 at 15:50











  • @bodhi.zazen, Yes, but do these work with sfill or zerofree?

    – sudodus
    Oct 3 '17 at 17:07











  • Possible duplicate of How to show the transfer progress and speed when copying files with cp?

    – karel
    Apr 10 '18 at 9:11














3












3








3


1






I want to wipe free space in my ubuntu partition and after a search found this sfill software which I installed using




sudo apt install secure-delete




Then I have used this command to wipe free space



$ sudo sfill -v /home
[sudo] password for shan:
Using /dev/urandom for random input.
Wipe mode is secure (38 special passes)
Wiping now ...
Creating /home/oooooooo.ooo ...


its stuck here for last 20 minutes and I don't know whether sfill is working or not. In my /home partion oooooooo.ooo file has a size of 27.6 MB and stays in this size. How to know the progress of wiping of free space in sfill?










share|improve this question
















I want to wipe free space in my ubuntu partition and after a search found this sfill software which I installed using




sudo apt install secure-delete




Then I have used this command to wipe free space



$ sudo sfill -v /home
[sudo] password for shan:
Using /dev/urandom for random input.
Wipe mode is secure (38 special passes)
Wiping now ...
Creating /home/oooooooo.ooo ...


its stuck here for last 20 minutes and I don't know whether sfill is working or not. In my /home partion oooooooo.ooo file has a size of 27.6 MB and stays in this size. How to know the progress of wiping of free space in sfill?







14.04 disk-usage secure-erase






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 3 '17 at 10:35









George Udosen

21.3k94570




21.3k94570










asked Oct 3 '17 at 9:02









EkaEka

1,05862139




1,05862139













  • There are many ways to show progress , see stackoverflow.com/questions/238073/…

    – Panther
    Oct 3 '17 at 15:50











  • @bodhi.zazen, Yes, but do these work with sfill or zerofree?

    – sudodus
    Oct 3 '17 at 17:07











  • Possible duplicate of How to show the transfer progress and speed when copying files with cp?

    – karel
    Apr 10 '18 at 9:11



















  • There are many ways to show progress , see stackoverflow.com/questions/238073/…

    – Panther
    Oct 3 '17 at 15:50











  • @bodhi.zazen, Yes, but do these work with sfill or zerofree?

    – sudodus
    Oct 3 '17 at 17:07











  • Possible duplicate of How to show the transfer progress and speed when copying files with cp?

    – karel
    Apr 10 '18 at 9:11

















There are many ways to show progress , see stackoverflow.com/questions/238073/…

– Panther
Oct 3 '17 at 15:50





There are many ways to show progress , see stackoverflow.com/questions/238073/…

– Panther
Oct 3 '17 at 15:50













@bodhi.zazen, Yes, but do these work with sfill or zerofree?

– sudodus
Oct 3 '17 at 17:07





@bodhi.zazen, Yes, but do these work with sfill or zerofree?

– sudodus
Oct 3 '17 at 17:07













Possible duplicate of How to show the transfer progress and speed when copying files with cp?

– karel
Apr 10 '18 at 9:11





Possible duplicate of How to show the transfer progress and speed when copying files with cp?

– karel
Apr 10 '18 at 9:11










2 Answers
2






active

oldest

votes


















3















zerofree and sfill



I think it enough for all the needs of ordinary people to overwrite once (and with zeros). You can do it with zerofree



sudo apt install zerofree

sudo zerofree /dev/sdxn


where x is the device letter and n is the partition number (for media devices probably sdb1).



Running sfill with 'wipe mode is secure (38 special passes)' needs 38 times longer time and will wear the drive 38 times more. Moreover is probably a waste of time.



You can use options to make it faster and (maybe) less secure. If I understand the manual correctly, sfill should work like zerofree when using the following options (but I have not tested).



sudo sfill -llz /path-to-mountpoint


or maybe they must be separate



sudo sfill -l -l -z /path-to-mountpoint


but you might as well let it write random data once



sudo sfill -l -l /path-to-mountpoint


I don't know if zerofree or sfill is more efficient (faster), when doing the same thing. (I need not guess here, but if you know, please edit this answer.)



According to the comment by @bodhi.zazen




Data can not be recovered if it is overwritten more than once




so the following command with sfill might be a good option (it overwrites twice),



sudo sfill -l /path-to-mountpoint


man sfill describes the option -l:




-l lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.




Low level wiping



If you really need this high level of security, it is better to backup or clone the data to another drive and wipe the drive with a special tool, that works on a lower level, for example hdparm or DBAN. It will be much more efficient (much faster).



It is possible to use re-linking between logical addresses and physical memory cells with hdparm. This is a kind of encryption rather than overwriting the whole memory and very efficient. I think the following link can help you use that method,



Re: best way to wipe a drive - with hdparm



After the low level wiping you can either restore the file data to the wiped drive or simply use it on the other drive (if cloned with Clonezilla, which clones used data blocks and skips free blocks).



How to know the progress or at least that something is happening



There is an option for verbose mode, -v. I see that you have already used it. I don't know any other way to make sfill tell you more, and it does not look like you get a progress view.



But if you want to know if the process is still doing something, you can try with iotop



sudo apt install iotop

sudo iotop -o





share|improve this answer





















  • 3





    Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

    – Panther
    Oct 3 '17 at 15:48






  • 1





    Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

    – sudodus
    Oct 3 '17 at 17:00



















2














I didn't find any way to directly monitor the progress of sfill but I myself found an indirect way to do this. The process for me took many hours I recommend to use small overwriting pass in sfill.



Open two terminals, in the first terminal start sfill



  #wiping free space in root drive
sudo sfill -v /


Now in the second terminal do these commands



  cd / #move to root direcotry where oooooooo.ooo exists
watch -n 30 "ls -lah|grep 'ooo'&&df -h|grep 'sdxn'"


watch -n 30 command lets you monitor a specific shell command in a particular interval of time (here 30sec) ls -lah|grep 'ooo' monitors the size of oooooooo.ooo and df -h|grep 'sdxn' monitors the size left in our root drive xn is the partion number. When sfill progress we can see our drive size decreasing gradually and when the available space reaches zero stop the process.






share|improve this answer

























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f961558%2fhow-to-know-the-progress-of-sfill-free-space-wiping-process%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3















    zerofree and sfill



    I think it enough for all the needs of ordinary people to overwrite once (and with zeros). You can do it with zerofree



    sudo apt install zerofree

    sudo zerofree /dev/sdxn


    where x is the device letter and n is the partition number (for media devices probably sdb1).



    Running sfill with 'wipe mode is secure (38 special passes)' needs 38 times longer time and will wear the drive 38 times more. Moreover is probably a waste of time.



    You can use options to make it faster and (maybe) less secure. If I understand the manual correctly, sfill should work like zerofree when using the following options (but I have not tested).



    sudo sfill -llz /path-to-mountpoint


    or maybe they must be separate



    sudo sfill -l -l -z /path-to-mountpoint


    but you might as well let it write random data once



    sudo sfill -l -l /path-to-mountpoint


    I don't know if zerofree or sfill is more efficient (faster), when doing the same thing. (I need not guess here, but if you know, please edit this answer.)



    According to the comment by @bodhi.zazen




    Data can not be recovered if it is overwritten more than once




    so the following command with sfill might be a good option (it overwrites twice),



    sudo sfill -l /path-to-mountpoint


    man sfill describes the option -l:




    -l lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.




    Low level wiping



    If you really need this high level of security, it is better to backup or clone the data to another drive and wipe the drive with a special tool, that works on a lower level, for example hdparm or DBAN. It will be much more efficient (much faster).



    It is possible to use re-linking between logical addresses and physical memory cells with hdparm. This is a kind of encryption rather than overwriting the whole memory and very efficient. I think the following link can help you use that method,



    Re: best way to wipe a drive - with hdparm



    After the low level wiping you can either restore the file data to the wiped drive or simply use it on the other drive (if cloned with Clonezilla, which clones used data blocks and skips free blocks).



    How to know the progress or at least that something is happening



    There is an option for verbose mode, -v. I see that you have already used it. I don't know any other way to make sfill tell you more, and it does not look like you get a progress view.



    But if you want to know if the process is still doing something, you can try with iotop



    sudo apt install iotop

    sudo iotop -o





    share|improve this answer





















    • 3





      Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

      – Panther
      Oct 3 '17 at 15:48






    • 1





      Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

      – sudodus
      Oct 3 '17 at 17:00
















    3















    zerofree and sfill



    I think it enough for all the needs of ordinary people to overwrite once (and with zeros). You can do it with zerofree



    sudo apt install zerofree

    sudo zerofree /dev/sdxn


    where x is the device letter and n is the partition number (for media devices probably sdb1).



    Running sfill with 'wipe mode is secure (38 special passes)' needs 38 times longer time and will wear the drive 38 times more. Moreover is probably a waste of time.



    You can use options to make it faster and (maybe) less secure. If I understand the manual correctly, sfill should work like zerofree when using the following options (but I have not tested).



    sudo sfill -llz /path-to-mountpoint


    or maybe they must be separate



    sudo sfill -l -l -z /path-to-mountpoint


    but you might as well let it write random data once



    sudo sfill -l -l /path-to-mountpoint


    I don't know if zerofree or sfill is more efficient (faster), when doing the same thing. (I need not guess here, but if you know, please edit this answer.)



    According to the comment by @bodhi.zazen




    Data can not be recovered if it is overwritten more than once




    so the following command with sfill might be a good option (it overwrites twice),



    sudo sfill -l /path-to-mountpoint


    man sfill describes the option -l:




    -l lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.




    Low level wiping



    If you really need this high level of security, it is better to backup or clone the data to another drive and wipe the drive with a special tool, that works on a lower level, for example hdparm or DBAN. It will be much more efficient (much faster).



    It is possible to use re-linking between logical addresses and physical memory cells with hdparm. This is a kind of encryption rather than overwriting the whole memory and very efficient. I think the following link can help you use that method,



    Re: best way to wipe a drive - with hdparm



    After the low level wiping you can either restore the file data to the wiped drive or simply use it on the other drive (if cloned with Clonezilla, which clones used data blocks and skips free blocks).



    How to know the progress or at least that something is happening



    There is an option for verbose mode, -v. I see that you have already used it. I don't know any other way to make sfill tell you more, and it does not look like you get a progress view.



    But if you want to know if the process is still doing something, you can try with iotop



    sudo apt install iotop

    sudo iotop -o





    share|improve this answer





















    • 3





      Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

      – Panther
      Oct 3 '17 at 15:48






    • 1





      Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

      – sudodus
      Oct 3 '17 at 17:00














    3












    3








    3








    zerofree and sfill



    I think it enough for all the needs of ordinary people to overwrite once (and with zeros). You can do it with zerofree



    sudo apt install zerofree

    sudo zerofree /dev/sdxn


    where x is the device letter and n is the partition number (for media devices probably sdb1).



    Running sfill with 'wipe mode is secure (38 special passes)' needs 38 times longer time and will wear the drive 38 times more. Moreover is probably a waste of time.



    You can use options to make it faster and (maybe) less secure. If I understand the manual correctly, sfill should work like zerofree when using the following options (but I have not tested).



    sudo sfill -llz /path-to-mountpoint


    or maybe they must be separate



    sudo sfill -l -l -z /path-to-mountpoint


    but you might as well let it write random data once



    sudo sfill -l -l /path-to-mountpoint


    I don't know if zerofree or sfill is more efficient (faster), when doing the same thing. (I need not guess here, but if you know, please edit this answer.)



    According to the comment by @bodhi.zazen




    Data can not be recovered if it is overwritten more than once




    so the following command with sfill might be a good option (it overwrites twice),



    sudo sfill -l /path-to-mountpoint


    man sfill describes the option -l:




    -l lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.




    Low level wiping



    If you really need this high level of security, it is better to backup or clone the data to another drive and wipe the drive with a special tool, that works on a lower level, for example hdparm or DBAN. It will be much more efficient (much faster).



    It is possible to use re-linking between logical addresses and physical memory cells with hdparm. This is a kind of encryption rather than overwriting the whole memory and very efficient. I think the following link can help you use that method,



    Re: best way to wipe a drive - with hdparm



    After the low level wiping you can either restore the file data to the wiped drive or simply use it on the other drive (if cloned with Clonezilla, which clones used data blocks and skips free blocks).



    How to know the progress or at least that something is happening



    There is an option for verbose mode, -v. I see that you have already used it. I don't know any other way to make sfill tell you more, and it does not look like you get a progress view.



    But if you want to know if the process is still doing something, you can try with iotop



    sudo apt install iotop

    sudo iotop -o





    share|improve this answer
















    zerofree and sfill



    I think it enough for all the needs of ordinary people to overwrite once (and with zeros). You can do it with zerofree



    sudo apt install zerofree

    sudo zerofree /dev/sdxn


    where x is the device letter and n is the partition number (for media devices probably sdb1).



    Running sfill with 'wipe mode is secure (38 special passes)' needs 38 times longer time and will wear the drive 38 times more. Moreover is probably a waste of time.



    You can use options to make it faster and (maybe) less secure. If I understand the manual correctly, sfill should work like zerofree when using the following options (but I have not tested).



    sudo sfill -llz /path-to-mountpoint


    or maybe they must be separate



    sudo sfill -l -l -z /path-to-mountpoint


    but you might as well let it write random data once



    sudo sfill -l -l /path-to-mountpoint


    I don't know if zerofree or sfill is more efficient (faster), when doing the same thing. (I need not guess here, but if you know, please edit this answer.)



    According to the comment by @bodhi.zazen




    Data can not be recovered if it is overwritten more than once




    so the following command with sfill might be a good option (it overwrites twice),



    sudo sfill -l /path-to-mountpoint


    man sfill describes the option -l:




    -l lessens the security. Only two passes are written: one mode with 0xff and a final mode with random values.




    Low level wiping



    If you really need this high level of security, it is better to backup or clone the data to another drive and wipe the drive with a special tool, that works on a lower level, for example hdparm or DBAN. It will be much more efficient (much faster).



    It is possible to use re-linking between logical addresses and physical memory cells with hdparm. This is a kind of encryption rather than overwriting the whole memory and very efficient. I think the following link can help you use that method,



    Re: best way to wipe a drive - with hdparm



    After the low level wiping you can either restore the file data to the wiped drive or simply use it on the other drive (if cloned with Clonezilla, which clones used data blocks and skips free blocks).



    How to know the progress or at least that something is happening



    There is an option for verbose mode, -v. I see that you have already used it. I don't know any other way to make sfill tell you more, and it does not look like you get a progress view.



    But if you want to know if the process is still doing something, you can try with iotop



    sudo apt install iotop

    sudo iotop -o






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 3 hours ago









    Pablo Bianchi

    2,94521535




    2,94521535










    answered Oct 3 '17 at 11:50









    sudodussudodus

    25.1k32977




    25.1k32977








    • 3





      Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

      – Panther
      Oct 3 '17 at 15:48






    • 1





      Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

      – sudodus
      Oct 3 '17 at 17:00














    • 3





      Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

      – Panther
      Oct 3 '17 at 15:48






    • 1





      Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

      – sudodus
      Oct 3 '17 at 17:00








    3




    3





    Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

    – Panther
    Oct 3 '17 at 15:48





    Data can not be recovered if it is overwritten more than once - The theory Peter Gutmann presented at a 1996 Usenix conference has been debunked - see nber.org/sys-admin/overwritten-data-guttman.html and stellarinfo.com/blog/… . Note the difference in the second article between deleted, trash, reformatted, and over written. The advice to use a program such as DBAN or similar to perform multiple passes is poor as it causes unnecessary wear on the device and takes much longer.

    – Panther
    Oct 3 '17 at 15:48




    1




    1





    Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

    – sudodus
    Oct 3 '17 at 17:00





    Thanks for the heads up, @bodhi.zazen. I edited the answer to add a paragraph about using hdparm. Please check that it is correct, and if not, please help me improve it.

    – sudodus
    Oct 3 '17 at 17:00













    2














    I didn't find any way to directly monitor the progress of sfill but I myself found an indirect way to do this. The process for me took many hours I recommend to use small overwriting pass in sfill.



    Open two terminals, in the first terminal start sfill



      #wiping free space in root drive
    sudo sfill -v /


    Now in the second terminal do these commands



      cd / #move to root direcotry where oooooooo.ooo exists
    watch -n 30 "ls -lah|grep 'ooo'&&df -h|grep 'sdxn'"


    watch -n 30 command lets you monitor a specific shell command in a particular interval of time (here 30sec) ls -lah|grep 'ooo' monitors the size of oooooooo.ooo and df -h|grep 'sdxn' monitors the size left in our root drive xn is the partion number. When sfill progress we can see our drive size decreasing gradually and when the available space reaches zero stop the process.






    share|improve this answer






























      2














      I didn't find any way to directly monitor the progress of sfill but I myself found an indirect way to do this. The process for me took many hours I recommend to use small overwriting pass in sfill.



      Open two terminals, in the first terminal start sfill



        #wiping free space in root drive
      sudo sfill -v /


      Now in the second terminal do these commands



        cd / #move to root direcotry where oooooooo.ooo exists
      watch -n 30 "ls -lah|grep 'ooo'&&df -h|grep 'sdxn'"


      watch -n 30 command lets you monitor a specific shell command in a particular interval of time (here 30sec) ls -lah|grep 'ooo' monitors the size of oooooooo.ooo and df -h|grep 'sdxn' monitors the size left in our root drive xn is the partion number. When sfill progress we can see our drive size decreasing gradually and when the available space reaches zero stop the process.






      share|improve this answer




























        2












        2








        2







        I didn't find any way to directly monitor the progress of sfill but I myself found an indirect way to do this. The process for me took many hours I recommend to use small overwriting pass in sfill.



        Open two terminals, in the first terminal start sfill



          #wiping free space in root drive
        sudo sfill -v /


        Now in the second terminal do these commands



          cd / #move to root direcotry where oooooooo.ooo exists
        watch -n 30 "ls -lah|grep 'ooo'&&df -h|grep 'sdxn'"


        watch -n 30 command lets you monitor a specific shell command in a particular interval of time (here 30sec) ls -lah|grep 'ooo' monitors the size of oooooooo.ooo and df -h|grep 'sdxn' monitors the size left in our root drive xn is the partion number. When sfill progress we can see our drive size decreasing gradually and when the available space reaches zero stop the process.






        share|improve this answer















        I didn't find any way to directly monitor the progress of sfill but I myself found an indirect way to do this. The process for me took many hours I recommend to use small overwriting pass in sfill.



        Open two terminals, in the first terminal start sfill



          #wiping free space in root drive
        sudo sfill -v /


        Now in the second terminal do these commands



          cd / #move to root direcotry where oooooooo.ooo exists
        watch -n 30 "ls -lah|grep 'ooo'&&df -h|grep 'sdxn'"


        watch -n 30 command lets you monitor a specific shell command in a particular interval of time (here 30sec) ls -lah|grep 'ooo' monitors the size of oooooooo.ooo and df -h|grep 'sdxn' monitors the size left in our root drive xn is the partion number. When sfill progress we can see our drive size decreasing gradually and when the available space reaches zero stop the process.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Jun 9 '18 at 11:52







        user364819

















        answered Apr 10 '18 at 9:10









        EkaEka

        1,05862139




        1,05862139






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f961558%2fhow-to-know-the-progress-of-sfill-free-space-wiping-process%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            GameSpot

            connect to host localhost port 22: Connection refused

            Getting a Wifi WPA2 wifi connection