As the person who wrote that suggestion mentions:
"Unsetting the schg flag on /Applications/CrashPlan.app might be a permanent
fix, but could in theory be unsafe, and CrashPlan would probably just
reactivate the flag on the next autoupdate anyway."
Sent from Ronni's iPad4
> On 13 Apr 2016, at 2:30 PM, Rosemary Spark <arkaysp...@gmail.com> wrote:
>
> Hi Ronni,
> I've been reading around.
>
> This was another suggestion
>
> sudo find /.MobileBackups.trash/ -flags +schg -exec chflags noschg {} \;
>
> from https://discussions.apple.com/thread/5750388?tstart=0
>
> Is this safe?
> It has the virtue of being simpler.
>
> Cheers
> Rosemary
>
>
> Rosemary Spark
> PO Box 781
> South Fremantle WA 6162 Australia
> Phone: + 61 8 94336609
> Mobile: 0414268043
> arkaysp...@gmail.com
>
>
>> On 11 April 2016 at 19:01, Ronni Brown <ro...@mac.com> wrote:
>> Hi Rosemary,
>>
>>> On 11 Apr 2016, at 12:13 PM, Rosemary Spark <arkaysp...@gmail.com> wrote:
>>>
>>> Hi Ronni,
>>> I found this discussion but I'm not that familiar with terminal
>>
>> After reading the complete log you sent in previous email, and knowing that
>> you are not very familiar with using Terminal.
>> The Terminal commands required are using sudo - and you need to be VERY
>> careful when using the sudo command.
>> You could type a command incorrectly and destroy the system!
>>
>> I would recommend you contact either Daniel or another consultant to come
>> and carry out the necessary procedures to fix this CrashPlan.app problem in
>> Time Machine backups.
>> As I mentioned before seeing the complete log…
>> /begin quote:
>> Without seeing the complete log file of your TM backupd just the parts of
>> the log below indicates to me CrashPlan is the problem.
>>
>> You would also see in the logs that TimeMachine is having issues thinning
>> old backups on TimeCapsule, and worse yet, TimeMachine won't thin the
>> MobileBackups on your Mac, meaning your SSD or hard drive will being filled
>> up by backups that would never be deleted.
>>
>> It seems when you install CrashPlan, it sets file system attributes that do
>> not allow itself to get deleted. With a bit of command-line wizardry, you
>> can fix this problem. You need to remove the attributes from all instances
>> of CrashPlan.app in all backed-up locations.
>> AND then Exclude CrashPlan from TM backups
>>
>> This Apple discussion should help you with the terminal commands:
>> <https://discussions.apple.com/message/29277434#29277434>
>> /end quote:
>>
>> Or if you don’t wish to wait until you can get an appointment with a
>> consultant, I would suggest you:
>> Start Again:
>> A) Erase the Data disk in Time Capsule (that will erase everything - both
>> computer backups (yours & your husbands).
>> 1. Open Airport Utility
>> 2. Select Time Capsule
>> 3. Then 'Edit'
>> 4. Then 'Disks'
>> 5. Then 'Erase Disk' button
>>
>> You will get a confirmation prompt, defaulted to "Quick Erase", which is
>> fine for most purposes.
>>
>> B) Then Exclude CrashPlan from TM backups
>> add /Applications/CrashPlan.app to the excluded list for TimeMachine backups
>> so that it is not backed up again.
>>
>> System Preferences > Time Machine - click on Options
>> exclude /Applications/CrashPlan.app from Time Machine.
>> Otherwise you will continue to create more problematic snapshots in Time
>> Machine.
>>
>>
>> Cheers,
>> Ronni
>>
>> 13-inch MacBook Air (April 2014)
>> 1.7GHz Dual-Core Intel Core i7, Turbo Boost to 3.3GHz
>> 8GB 1600MHz LPDDR3 SDRAM
>> 512GB PCIe-based Flash Storage
>>
>> El Capitan OS X 10.11.4
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>
