# Errors when creating snapshot of home dir

**URL:** https://kopia.discourse.group/t/errors-when-creating-snapshot-of-home-dir/81
**Category:** Support
**Created:** [September 4, 2020, 11:54pm UTC](https://kopia.discourse.group/t/errors-when-creating-snapshot-of-home-dir/81 "2020-09-04T23:54:26Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![gumper](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@gumper](https://kopia.discourse.group/u/gumper)
#### Post date: [September 4, 2020, 11:54pm UTC](https://kopia.discourse.group/t/errors-when-creating-snapshot-of-home-dir/81/1 "2020-09-04T23:54:26Z")

</div>

I’m trying to create a snapshot of my Linux home directory, but when doing so I’m getting the following errors as well as other errors:

> | 0 hashing, 0 hashed (0 B), 1 cached (79 B), 0 uploaded (0 B), 0 errors 0.0%19:46:19.156 [kopia/localfs] unable to create directory entry “.SR\_BEACON\_LINUXRead”: unsupported filesystem entry: &{.SR\_BEACON\_LINUXRead 0 33554870 {652912100 63720091870 0x1b21580} {64770 664285 1 4534 1000 1000 0 0 0 4096 0 {1584495070 652912100} {1584495070 652912100} {1598400280 863783408} [0 0 0]}}  
> 19:46:19.156 [kopia/localfs] unable to create directory entry “.ipc\_pipe.43560”: unsupported filesystem entry: &{.ipc\_pipe.43560 0 33554816 {136400008 63734848346 0x1b21580} {64770 664535 1 4480 1000 1000 0 0 0 4096 0 {1599251546 136400008} {1599251546 136400008} {1599251546 136400008} [0 0 0]}}  
> 19:46:19.156 [kopia/localfs] unable to create directory entry “.AuthManagerSSOnPipe.request”: unsupported filesystem entry: &{.AuthManagerSSOnPipe.request 0 33554816 {396792214 63720000532 0x1b21580} {64770 664288 1 4480 1000 1000 0 0 0 4096 0 {1584403732 396792214} {1584403732 396792214} {1584403732 396792214} [0 0 0]}}

Any idea what would be causing these errors?

---

<div class="post-metadata">

### Author: ![jkowalski](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jkowalski/32/3_2.png) [@jkowalski](https://kopia.discourse.group/u/jkowalski)
#### Post date: [September 4, 2020, 11:56pm UTC](https://kopia.discourse.group/t/errors-when-creating-snapshot-of-home-dir/81/2 "2020-09-04T23:56:18Z")

</div>

Yes. Named pipes are not supported yet and will be skipped. Those are warnings not errors so everything else should be backed up.

---

<div class="post-metadata">

### Author: ![gumper](https://avatars.discourse-cdn.com/v4/letter/g/bc8723/32.png) [@gumper](https://kopia.discourse.group/u/gumper)
#### Post date: [September 5, 2020, 1:13am UTC](https://kopia.discourse.group/t/errors-when-creating-snapshot-of-home-dir/81/3 "2020-09-05T01:13:26Z")

</div>

Great. Glad that it’s nothing to worry about.

---

<div class="post-metadata">

### Author: ![b3ta](https://avatars.discourse-cdn.com/v4/letter/b/2acd7d/32.png) [@b3ta](https://kopia.discourse.group/u/b3ta)
#### Post date: [March 3, 2025, 4:19pm UTC](https://kopia.discourse.group/t/errors-when-creating-snapshot-of-home-dir/81/4 "2025-03-03T16:19:54Z")

</div>

> Yes. Named pipes are not supported yet and will be skipped. Those are warnings not errors so everything else should be backed up.

Is there a way to tell a snapshot not even to try backing up things like named pipes?

I’d far rather be in a position to tell users that every reported error is an error — that way they won’t miss important ones because they ignore unimportant ones every time a snapshot is taken.
