Damn it! Everything working fine yesterday morning. Computer only used for backups. Latest UrBackup v.2.4.13 server using a BTRFS filesystem for backups. I have plenty of space on single partition btrfs filesystem (~20% of 6.5TB). I don’t know how many file descriptors are available, but lsof | wc -l returns 17058. Rebooted. Now I get multiple lines in log file:
Yes, it is in readonly - Also, looking at dmesg I can see that it was forced to readonly. I’ve tried btrfs scrub and find that the partition has 4 uncorrectable errors. Then, trying btrfs check --repair ends in a segmentation fault.
I only have one drive at this time. Thanks for the link - I will check it out.
I ended up mucking it up while trying to repair it. I just can’t seem to run urbackup to a btrfs partition longer than a year or so before the filesystem forces itself to readonly. I’ve never had an issue (with filesystem corruption) using ext4 for a file server. Not the same workload, but not idle very long either.
I ran mkfs.btrfs on the partition and am starting over. Again. I’ll feel better in a few days when all clients have had a chance to backup.