You are not logged in.
Don't know if this fits here.
I (might) have done something very stupid. I wanted to compile something, but I always ran out of virtual memory. So I decided to get me some more swap, by means of creating a swap file using dd.
The problem is, I didn't check for available space, which was - unbeknown to me - less than the 8GiB I just requested from dd.
Consequently, df showed 100% disk use, and after a reboot, I deleted the swap file. Running fsck from a stick didn't amount to anything, so my question is:
(How) can I find out which files I possibly corrupted? Because there just have to be some.
Offline
You have to be more specific, tell us how you used dd, post the full command line.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Well, basically I ran something like
$ dd bs=1M if=/dev/zero of=/mnt/file.swap count=8192
$ mkswap /mnt/file.swap
$ swapon /mnt/file.swap
This should pretty much be the command, although I can't say it with certainty, as no bash history was saved (no disk space was available).
Or is dd smart enough to anticipate a luser like me?
Last edited by jo.be (2016-07-25 09:54:44)
Offline
Everything should be ok, when the filesystem got full it stopped writing, just like it would in a normal file copy. The only catch is the files that were open and still had data waiting to be flushed might be missing that data. This includes temporary files, log files and DE session files, system files should be fine.
R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K
Offline
Not a Sysadmin issue, moving to NC...
Offline