# Awareness between Local Persistent Volume and StatefulSet

**URL:** <https://discuss.kubernetes.io/t/awareness-between-local-persistent-volume-and-statefulset/9789>\
**Category:** General Discussions\
**Created:** [February 19, 2020, 6:20pm UTC](https://discuss.kubernetes.io/t/awareness-between-local-persistent-volume-and-statefulset/9789 "2020-02-19T18:20:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kennthhz](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/kennthhz/32/4618_2.png) [@kennthhz](https://discuss.kubernetes.io/u/kennthhz)\
**Post date:** [February 19, 2020, 6:20pm UTC](https://discuss.kubernetes.io/t/awareness-between-local-persistent-volume-and-statefulset/9789/1 "2020-02-19T18:20:34Z")

</div>

I have two questions in this area

1. If disk of local persistent volume goes back, but POD (container process) is still healthy, will K8s be aware and signal in anyway? or monitoring and dealing this is purely the responsibility of the application?

2. When POD is destroyed or moved to a different node, is application’s responsibility to create a new local persistent volume at the new node and recover/copy the data? Will K8s generate some kind of notification that tells the old and new POD location?