Weird empty directories in root (/)

beta990 · 2016-05-16 11:42:13

# ls -lh /
total 20K
drwxr-xr-x   1 root root    0 May 15 16:30 -6f818f36fc395bf8-0000000000
drwxr-xr-x   1 root root    0 May 15 15:06 ''\''-727b9ce727b9ce72-0000000000'
lrwxrwxrwx   1 root root    7 Sep 30  2015 bin -> usr/bin
drwxr-xr-x   4 root root 4.0K Jan  1  1970 boot
drwxr-xr-x  18 root root 3.1K May 16 13:21 dev
drwxr-xr-x   1 root root    0 May 15 15:46 -ec685e9a506c6046-0000000000
drwxr-xr-x   1 root root 2.6K May 16 13:23 etc
drwxr-xr-x   1 root root    0 May 15 16:25 -f0277d82a6f67b9f-0000000000
drwxr-xr-x   1 root root   28 Dec 29  2014 home
lrwxrwxrwx   1 root root    7 Sep 30  2015 lib -> usr/lib
lrwxrwxrwx   1 root root    7 Sep 30  2015 lib64 -> usr/lib
drwxrwxr-x   1 root root   14 May  7 20:58 mnt
drwxr-xr-x   1 root root   14 Mar 20 17:31 opt
dr-xr-xr-x 220 root root    0 May 15 16:34 proc
drwxr-x---   1 root root  268 May 16 02:30 root
drwxr-xr-x  21 root root  660 May 16 13:23 run
lrwxrwxrwx   1 root root    7 Sep 30  2015 sbin -> usr/bin
drwxr-xr-x   1 root root   26 Nov  1  2014 srv
dr-xr-xr-x  13 root root    0 May 16 13:19 sys
drwxrwxrwt  13 root root  500 May 16 13:33 tmp
drwxr-xr-x   1 root root   96 Mar 25 11:31 usr
drwxr-xr-x   1 root root  116 Jan 18 12:56 var

Scanned with clamav, now going to scan with rkhunter.
Don't think it's a virus/hacker, since the NAS is only accessible using an OpenVPN connection (with certificates) and I'm not seeing any weird users/processes.
The ssh connection is also protected using Google-Authenticator.

Could it be an issue with my old Intel 330 SSD (running on btrfs)?
System is up-to-date.

When removing these empty directories, they are replaced with new empty directories (don't know when, but I suspect after a reboot).

Many thanks.

# clamscan --recursive=yes --infected /
----------- SCAN SUMMARY -----------
Known viruses: 4357079
Engine version: 0.99.2
Scanned directories: 29744
Scanned files: 121646
Infected files: 0
Total errors: 19527
Data scanned: 7768.01 MB
Data read: 276928.92 MB (ratio 0.03:1)
Time: 507.491 sec (8 m 27 s)

[13:45:19] System checks summary
[13:45:19] =====================
[13:45:19]
[13:45:19] File properties checks...
[13:45:20] Files checked: 121
[13:45:20] Suspect files: 6
[13:45:20]
[13:45:20] Rootkit checks...
[13:45:20] Rootkits checked : 216
[13:45:20] Possible rootkits: 0
[13:45:20]
[13:45:20] Applications checks...
[13:45:20] Applications checked: 4
[13:45:20] Suspect applications: 0
[13:45:20]
[13:45:20] The system checks took: 1 minute and 5 seconds
[13:45:20]
[13:45:20] Info: End date is Mon May 16 13:45:20 CEST 2016

Last edited by beta990 (2016-05-16 11:48:12)

WorMzy · 2016-05-16 13:37:57

Check your journal. What happened around May 15 16:30? That's when -6f818f36fc395bf8-0000000000 was created.

What filesystem are you using for /?

beta990 · 2016-05-16 19:33:49

WorMzy wrote:

Check your journal. What happened around May 15 16:30? That's when -6f818f36fc395bf8-0000000000 was created.
What filesystem are you using for /?

Thanks for your reply.

Using btrfs as filesystem, the only thing I see is scrub process started/stoped for '/' and some MySQL database errors.

Last edited by beta990 (2016-05-18 13:42:29)

drcouzelis · 2016-05-16 20:07:07

This is kind of a fun question.

Can you please post your list of systemd services? And installed packages? Have you installed anything without using pacman?

Head_on_a_Stick · 2016-05-16 20:31:46

beta990 wrote:

old Intel 330 SSD

Can you be sure that the drive health is good?

R00KIE · 2016-05-16 21:08:31

Shouldn't btrfs detect (and log to dmesg) if something is not correct with the checksum feature? That said check what smartctl has to say about the health of the ssd.

beta990 · 2016-05-17 10:11:31

drcouzelis wrote:

This is kind of a fun question.
Can you please post your list of systemd services? And installed packages? Have you installed anything without using pacman?

Hi drcouzelis,

Few AUR packages with pacaur, nothing special.
This is the list of enabled.

Head_on_a_Stick wrote:

beta990 wrote:
old Intel 330 SSD
Can you be sure that the drive health is good?

R00KIE wrote:

Shouldn't btrfs detect (and log to dmesg) if something is not correct with the checksum feature? That said check what smartctl has to say about the health of the ssd.

$ sudo smartctl -a -H /dev/sda
smartctl 6.4 2015-06-04 r4109 [x86_64-linux-4.5.3-1-ck] (local build)
Copyright (C) 2002-15, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Intel 330/335 Series SSDs
Device Model:     INTEL SSDSC2CT060A3
Serial Number:    
LU WWN Device Id: 5 001517 bb28a3eaf
Firmware Version: 300i
User Capacity:    60,022,480,896 bytes [60.0 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue May 17 12:13:55 2016 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                (  732) seconds.
Offline data collection
capabilities:                    (0x7f) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Abort Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (  48) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x0021) SCT Status supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0032   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours_and_Msec 0x0032   000   000   000    Old_age   Always       -       912469h+43m+11.990s
 12 Power_Cycle_Count       0x0032   098   098   000    Old_age   Always       -       2450
181 Program_Fail_Cnt_Total  0x0032   000   000   000    Old_age   Always       -       0
182 Erase_Fail_Count_Total  0x0032   000   000   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       1337
225 Host_Writes_32MiB       0x0032   100   100   000    Old_age   Always       -       265663
232 Available_Reservd_Space 0x0033   100   100   010    Pre-fail  Always       -       0
233 Media_Wearout_Indicator 0x0032   100   100   000    Old_age   Always       -       0
241 Host_Writes_32MiB       0x0032   100   100   000    Old_age   Always       -       265663
242 Host_Reads_32MiB        0x0032   100   100   000    Old_age   Always       -       142510
249 NAND_Writes_1GiB        0x0013   100   100   000    Pre-fail  Always       -       9533

SMART Error Log not supported

SMART Self-test Log not supported

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

----

No weird folders at the moment, seems to only happen on a reboot. :S

Last edited by beta990 (2016-05-17 10:15:22)

R00KIE · 2016-05-17 13:11:04

SSD smart parameters look fine. No other ideas here except trying to rule out other hardware problems (memory / cpu - overclock/overheating) before assuming you are dealing with a bug, which might be the case.

beta990 · 2016-05-17 13:59:51

R00KIE wrote:

SSD smart parameters look fine. No other ideas here except trying to rule out other hardware problems (memory / cpu - overclock/overheating) before assuming you are dealing with a bug, which might be the case.

Think this issue is SSD (Btrfs?) related, because it doesn't happen on my other drivers (that are formatted as ext4).
The Intel 330 isn't the best SSD as it doesn't offer any protection against resets/hard shutdowns (although I use proper ACPI-methods).
My guess is the SSD that isn't proper unmounted/power fails on a reboot/shutdown.

Think it's better to keep the NAS running atm.

Last edited by beta990 (2016-05-17 14:00:40)

drcouzelis · 2016-05-17 15:11:00

Here is a possibly related post: http://www.spinics.net/lists/linux-btrfs/msg17609.html

SPOILER: It might be a corrupted filesystem.

beta990 · 2016-05-17 19:59:43

drcouzelis wrote:

Here is a possibly related post: http://www.spinics.net/lists/linux-btrfs/msg17609.html
SPOILER: It might be a corrupted filesystem.

Thanks, seems running btrfs.fsck may fix this problem.
So far so good, maybe next week.

R00KIE · 2016-05-17 20:42:29

Make sure you keep backups of important things. It is working fine now but if you don't find the root cause of the problem it might break monumentally at any time.

beta990 · 2016-05-18 08:20:50

R00KIE wrote:

Make sure you keep backups of important things. It is working fine now but if you don't find the root cause of the problem it might break monumentally at any time.

Thanks, I always make backups of my important config, db's, etc.

I will wait with running btrfs.fsck, since it may break more stuff then it repairs.

Last edited by beta990 (2016-05-18 08:21:03)

EdeWolf · 2016-05-18 12:26:45

Just for the record: I've lost a complete partition with running btrfs.fsck. That is, it was completely empty after running it. So being careful is adviced. Not sure, what I did wrong, surely something, just seconding to be careful.

WorMzy · 2016-05-18 12:57:39

To clarify, there is no btrfs.fsck. There is 'btrfs check', but this command should be used with care. As EdeWolf says, it can bork a filesystem even more than it currently is.

drcouzelis · 2016-05-18 13:45:29

That's it, I'm sticking with nice, boring Ext and it's sequels for the next decade. O_o

beta990 · 2016-05-18 13:47:40

EdeWolf wrote:

Just for the record: I've lost a complete partition with running btrfs.fsck. That is, it was completely empty after running it. So being careful is adviced. Not sure, what I did wrong, surely something, just seconding to be careful.

WorMzy wrote:

To clarify, there is no btrfs.fsck. There is 'btrfs check', but this command should be used with care. As EdeWolf says, it can bork a filesystem even more than it currently is.

Thanks!
I had read a few topics of users losing their files after running fsck/btrfs check (although it was in the early days), good to see it confirmed here.
Think I'm better of doing a (clean) reinstall.

Anyway, thanks again for the all the help, and glad it's not a virus of some sort.

beta990 · 2016-06-04 15:13:25

And it's back:

# ls -lh /
total 20K
drwxr-xr-x   1 root root    0 May 27 16:25 -0000000000000000-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:44 -02ecb7a516a9a21f-0000000000
drwxr-xr-x   1 root root    0 May 22 17:27 -06620c8220647dcf-0000000000
drwxr-xr-x   1 root root    0 May 22 17:12 '0`-922583c1ffd2e060-0000000000'
drwxr-xr-x   1 root root    0 May 22 16:25 -0abdc2cb70af4fa9-0000000000
drwxr-xr-x   1 root root    0 May 24 20:06 0-b6e6207a69085288-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:11 -0ef0712a2e68304c-0000000000
drwxr-xr-x   1 root root    0 May 27 16:46 -14025ab9b7687ada-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:59 -148694a25030f446-0000000000
drwxr-xr-x   1 root root    0 May 20 20:36 -192ced114a2ea022-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:49 -1add3f08e608e778-0000000000
drwxr-xr-x   1 root root    0 May 27 13:41 1-e3ae1e5fcff7a2af-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:56 -1e731fbde510f26d-0000000000
drwxr-xr-x   1 root root    0 May 22 17:10 -1eecebfa0e7469b4-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:26 -2a175ae1d7705a67-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:37 -2ae9be314332e9a3-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:24 -2ea283cb6d455412-0000000000
drwxr-xr-x   1 root root    0 May 20 20:40 -2f4e53edcaff18a0-0000000000
drwxr-xr-x   1 root root    0 May 20 19:59 -2fbac33896b2e6b3-0000000000
drwxr-xr-x   1 root root    0 May 24 19:51 '|?-3096a810c199e118-0000000000'
drwxr-xr-x   1 root root    0 May 22 16:52 -31776260000000ff-0000000000
drwxr-xr-x   1 root root    0 May 29 18:07 -3212372337210f01-0000000000
drwxr-xr-x   1 root root    0 Jun  4 14:27 -333212372337210f-0000000000
drwxr-xr-x   1 root root    0 May 20 21:02 -39ce4f739ce4f739-0000000000
drwxr-xr-x   1 root root    0 May 27 23:33 -3a3a3a3a3a3a3a3a-0000000000
drwxr-xr-x   1 root root    0 May 20 20:03 -3ce6d74240645e38-0000000000
drwxr-xr-x   1 root root    0 May 22 17:26 3QO-46b7af8f5390cae1-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:47 -41f8bb014b0e36b1-0000000000
drwxr-xr-x   1 root root    0 May 27 17:48 -44b4b83b1099ca5e-0000000000
drwxr-xr-x   1 root root    0 May 24 20:10 -4b419db5e60b7d7b-0000000000
drwxr-xr-x   1 root root    0 May 27 16:41 -4c77284260220634-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:39 ';-536b4582c5aaf543-0000000000'
drwxr-xr-x   1 root root    0 May 22 17:23 -5718ac79a3076038-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:47 -5745464e27742386-0000000000
drwxr-xr-x   1 root root    0 May 20 20:59 -5fed5ebcc8218210-0000000000
drwxr-xr-x   1 root root    0 May 20 20:55 -600cbb48b48e8cfa-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:20 -60b9bd4052003cd2-0000000000
drwxr-xr-x   1 root root    0 May 20 19:56 -6186e7d946f5d5a5-0000000000
drwxr-xr-x   1 root root    0 May 22 16:40 -61fe7fff0e7fff60-0000000000
drwxr-xr-x   1 root root    0 May 22 16:32 -6564836c25183ed7-0000000000
drwxr-xr-x   1 root root    0 May 24 20:21 -672ff94a5c15f98a-0000000000
drwxr-xr-x   1 root root    0 May 29 17:48 -68c17d59976d3fec-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:22 -690962cf81971004-0000000000
drwxr-xr-x   1 root root    0 May 27 12:46 -6bacc3b212403005-0000000000
drwxr-xr-x   1 root root    0 May 27 13:08 -7774ae5c22b279c9-0000000000
drwxr-xr-x   1 root root    0 May 27 17:38 -7de189fb7d786dcc-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:16 -7e9b4c29030402e0-0000000000
drwxr-xr-x   1 root root    0 May 27 17:28 -86e9bf0e5a6dab6c-0000000000
drwxr-xr-x   1 root root    0 May 24 20:34 8-70b78bb0dd2cd949-0000000000
drwxr-xr-x   1 root root    0 May 29 17:50 -8b2f8734b88ca890-0000000000
drwxr-xr-x   1 root root    0 May 20 21:07 -8c599b51a8d09a82-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:49 '[-8c8db9beb95bd8f6-0000000000'
drwxr-xr-x   1 root root    0 May 27 13:35 -8dc636c28e031a21-0000000000
drwxr-xr-x   1 root root    0 May 27 16:16 --8fa6819c5d8fae4e-0000000000
drwxr-xr-x   1 root root    0 May 27 17:57 -90ae26db3ee6fd6a-0000000000
drwxr-xr-x   1 root root    0 May 27 13:12 -9330306463060600-0000000000
drwxr-xr-x   1 root root    0 May 22 16:22 -96eb0eb4d0eb99dc-0000000000
drwxr-xr-x   1 root root    0 May 29 17:45 -976d3fecb44a4e2f-0000000000
drwxr-xr-x   1 root root    0 May 27 17:51 -9a681d814aaa9f2e-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:15 -9e0c87c2c187c890-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:32 9t-5a295d58ac4271d3-0000000000
drwxr-xr-x   1 root root    0 May 29 17:53 -a18a208b2f8734b8-0000000000
drwxr-xr-x   1 root root    0 May 27 13:26 -a18d4b103d439d24-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:17 -a22a9b4d960dbfa6-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:34 -a8326a853902a21e-0000000000
drwxr-xr-x   1 root root    0 May 27 17:59 -b008e6d1860c7030-0000000000
drwxr-xr-x   1 root root    0 May 27 17:54 -b019e14c00b12818-0000000000
drwxr-xr-x   1 root root    0 May 27 17:41 -b062d0700701c551-0000000000
drwxr-xr-x   1 root root    0 May 22 16:55 -b3023b29c7e5fad0-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:27 -b6e1ebae53e63db4-0000000000
drwxr-xr-x   1 root root    0 May 22 17:17 @B6J-3018c7e5baac71cb-0000000000
drwxr-xr-x   1 root root    0 May 27 13:37 -b7e18db6fc31b6df-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:36 'b`-80c35389dbbeb329-0000000000'
drwxr-xr-x   1 root root    0 May 22 16:48 -b859d5d7d8db0c1e-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:31 -b874e2c1577ecd67-0000000000
drwxr-xr-x   1 root root    0 May 20 20:27 -b91eb474fcca701e-0000000000
drwxr-xr-x   1 root root    0 May 20 21:20 -ba9f86a537dce729-0000000000
drwxr-xr-x   1 root root    0 May 22 17:20 -bf26de984a0c1000-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:02 -bf790120956de94b-0000000000
lrwxrwxrwx   1 root root    7 Sep 30  2015 bin -> usr/bin
drwxr-xr-x   4 root root 4.0K Jan  1  1970 boot
drwxr-xr-x   1 root root    0 May 27 13:16 -c66443928a3e112a-0000000000
drwxr-xr-x   1 root root    0 May 20 20:17 -c6de7e18db7fc31b-0000000000
drwxr-xr-x   1 root root    0 Jun  4 17:10 -c6dffe1a5fe7f3bc-0000000000
drwxr-xr-x   1 root root    0 Jun  4 16:28 -cb8b9fedcdcb3180-0000000000
drwxr-xr-x   1 root root    0 May 27 12:43 -cd675cdd229777aa-0000000000
drwxr-xr-x   1 root root    0 May 24 20:30 -cdeb83256aaf60d1-0000000000
drwxr-xr-x   1 root root    0 May 27 13:20 ''$'\177''-ce0c6090ef7431bc-0000000000'
drwxr-xr-x   1 root root    0 Jun  4 15:41 -d6a2e9e922783404-0000000000
drwxr-xr-x   1 root root    0 May 20 20:49 -d6b91f07a48a878e-0000000000
drwxr-xr-x   1 root root    0 May 27 17:45 '*~-d95e0786886700f2-0000000000'
drwxr-xr-x  18 root root 3.1K May 16 13:21 dev
drwxr-xr-x   1 root root    0 Jun  4 17:06 -e18de6fc315b7df7-0000000000
drwxr-xr-x   1 root root    0 May 24 20:01 -e1dfc59e1c52e889-0000000000
drwxr-xr-x   1 root root    0 May 27 16:44 -e70e4a71efcb39e5-0000000000
drwxr-xr-x   1 root root 2.6K Jun  4 14:11 etc
drwxr-xr-x   1 root root    0 Jun  4 16:42 -f06e314a68f71621-0000000000
drwxr-xr-x   1 root root    0 May 20 19:53 -f43c67e7b6fb869e-0000000000
drwxr-xr-x   1 root root    0 May 22 16:36 -f5b0d10d747b775b-0000000000
drwxr-xr-x   1 root root    0 May 27 17:07 -fabc5c86c5022d58-0000000000
drwxr-xr-x   1 root root    0 May 20 20:45 +]-fe56631efa94baf4-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:24 -ff8623f241fc31b6-0000000000
drwxr-xr-x   1 root root    0 May 22 16:44 -ffffffffff303177-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:51 Gu-258f84b6e438145e-0000000000
drwxr-xr-x   1 root root   28 Dec 29  2014 home
drwxr-xr-x   1 root root    0 May 27 13:44 i-691614b7777fb74a-0000000000
drwxr-xr-x   1 root root    0 May 22 16:29 K-223237b8b8c0e890-0000000000
lrwxrwxrwx   1 root root    7 Sep 30  2015 lib -> usr/lib
lrwxrwxrwx   1 root root    7 Sep 30  2015 lib64 -> usr/lib
drwxr-xr-x   1 root root    0 May 27 17:18 M{KaE-84636db485f569d2-0000000000
drwxrwxr-x   1 root root   14 May  7 20:58 mnt
drwxr-xr-x   1 root root    0 May 22 17:06 ng-455fcbaa6f6af0e0-0000000000
drwxr-xr-x   1 root root    0 May 24 19:56 'O?-554ad3373be4ed56-0000000000'
drwxr-xr-x   1 root root   24 May 22 17:13 opt
drwxr-xr-x   1 root root    0 May 20 20:21 P-754d5b066340384a-0000000000
dr-xr-xr-x 246 root root    0 May 15 16:34 proc
drwxr-xr-x   1 root root    0 May 27 12:39 q-427577b3d1626b1a-0000000000
drwxr-xr-x   1 root root    0 May 24 20:25 r-08673bce542e3b52-0000000000
drwxr-xr-x   1 root root    0 May 27 13:03 r-a6628a4a6454ffff-0000000000
drwxr-x---   1 root root  286 May 22 16:54 root
drwxr-xr-x  21 root root  680 Jun  1 11:32 run
lrwxrwxrwx   1 root root    7 Sep 30  2015 sbin -> usr/bin
drwxr-xr-x   1 root root   26 Nov  1  2014 srv
dr-xr-xr-x  13 root root    0 May 16 13:19 sys
drwxrwxrwt  17 root root  480 Jun  4 17:11 tmp
drwxr-xr-x   1 root root    0 May 27 12:57 ULAME3.92UUUUUUUUUUUUUUUUUUUUUUU-5555555555555555-0000000000
drwxr-xr-x   1 root root   96 Mar 25 11:31 usr
drwxr-xr-x   1 root root  116 Jan 18 12:56 var
drwxr-xr-x   1 root root    0 May 27 16:52 '^V?-ffffffffffffffff-0000000000'
drwxr-xr-x   1 root root    0 May 24 20:15 w-c08c78a8c7220833-0000000000
drwxr-xr-x   1 root root    0 Jun  4 15:44 wQ88-4c267a67a95eb53b-0000000000
drwxr-xr-x   1 root root    0 May 27 12:50 '[y-b78637dbf03cb6dd-0000000000'

Think I'm better of buying a new SSD.

Jeroen)Mathon · 2016-08-18 11:56:54

drcouzelis wrote:

That's it, I'm sticking with nice, boring Ext and it's sequels for the next decade. O_o

To be honest the Extended filesystem is in my opinion one of the most stable.

So i suggest sticking with it as well.

beta990 · 2016-08-30 08:50:22

Switched back to ext4, no issues so far.
Don't know why it happen, but it seems indeed filesystem corruption.

Still using btrfs for my /mnt/data in RAID1, so far so good. :X

Jeroen)Mathon · 2016-08-30 10:55:16

beta990

Could you mark this thread as solved?

null · 2016-08-30 16:01:39

beta990 wrote:

9 Power_On_Hours_and_Msec 0x0032   000   000   000    Old_age   Always       -       912469h+43m+11.990s

Just curious, where did you buy this disk back in good old 1912?

Arch Linux

#1 2016-05-16 11:42:13

Weird empty directories in root (/)

#2 2016-05-16 13:37:57

Re: Weird empty directories in root (/)

#3 2016-05-16 19:33:49

Re: Weird empty directories in root (/)

#4 2016-05-16 20:07:07

Re: Weird empty directories in root (/)

#5 2016-05-16 20:31:46

Re: Weird empty directories in root (/)

#6 2016-05-16 21:08:31

Re: Weird empty directories in root (/)

#7 2016-05-17 10:11:31

Re: Weird empty directories in root (/)

#8 2016-05-17 13:11:04

Re: Weird empty directories in root (/)

#9 2016-05-17 13:59:51

Re: Weird empty directories in root (/)

#10 2016-05-17 15:11:00

Re: Weird empty directories in root (/)

#11 2016-05-17 19:59:43

Re: Weird empty directories in root (/)

#12 2016-05-17 20:42:29

Re: Weird empty directories in root (/)

#13 2016-05-18 08:20:50

Re: Weird empty directories in root (/)

#14 2016-05-18 12:26:45

Re: Weird empty directories in root (/)

#15 2016-05-18 12:57:39

Re: Weird empty directories in root (/)

#16 2016-05-18 13:45:29

Re: Weird empty directories in root (/)

#17 2016-05-18 13:47:40

Re: Weird empty directories in root (/)

#18 2016-06-04 15:13:25

Re: Weird empty directories in root (/)

#19 2016-08-18 11:56:54

Re: Weird empty directories in root (/)

#20 2016-08-30 08:50:22

Re: Weird empty directories in root (/)

#21 2016-08-30 10:55:16

Re: Weird empty directories in root (/)

#22 2016-08-30 16:01:39

Re: Weird empty directories in root (/)

Board footer