Hard disk – DISKPART: Extended partition can not be deleted

I tried to convert my MBR hard drive with MBR2GPT to a GPT hard drive. I first checked the partition list with DiskPart and found that there are 4 partitions:

DISKPART> list partition
Partition ### type size offset
------------- ---------------- ------- -------
Partition 1 primary 49 GB 31 KB
Partition 0 Advanced 415 GB 50 GB
Partition 3 Logical 200 GB 50 GB
Partition 4 Logical 215 GB 250 GB

I checked the extended partition:

DISKPART> Detail Partition
Partition 0
Type: 0F
Hidden: No.
Active: no
Offset in Bytes: 53801556480

There is no volume associated with this partition.

I tried to delete it, but the following error occurred:

DISKPART> Delete partition

Virtual Disk Service Error:
The extended partition is not empty.

I tried to format it, but apparently I can not format the extended partition.

postgresql – Materialized view rights can not be deleted by the user

Legacy database for me, pg version 9.6.12 runs on a Linux Ami.

I have a user (& # 39; example_user & # 39;) whom I want to delete. I have confirmed that & # 39; example_user & # 39; has no objects. But when I run DROP USER & # 39; example_user & # 39 ;; I get the following error (cut off for brevity):

exampledb = # user & # 39; example_user & # 39; Clear;
ERROR: The role & # 39; example_user & # 39; can not be deleted because some objects depend on it
DETAIL: Permissions for materialized view "example-prod" .view_foo
Permissions for materialized view "example-prod" .view_bar
Permissions for materialized view "example-dev" .view_foo
Permissions for materialized view "example-dev" .view_bar

I've tried about 15 different revocation statements to kill the privileges, and in some cases, Postgres does not even complain. For example:

exampledb = # "example_user" revokes all permissions on all tables in the public scheme;

# OR

revoke all permissions for example-prod ".view_foo from" example_user ";

I've tried countless different revocations of each schema, view, database, and nothing seems to work. The permissions are not removed and I get the same error messages when I try to delete the user. I am not sure if it is related in any way, but pg complains if I do not double quote the user.

How can these specific or indeed all permissions be removed from this user? Are there any other strategies to delete this user if I do not have to worry about keeping objects or permissions?

Many Thanks!

mysql tables with engines of "MEMORY" are not deleted when the server is restarted

I've read a description of using MEMORY or NDB clusters
from the MySQL website.

Transactions with temporary, non-critical data, such as Eg session
Management or caching. When the MySQL server is stopped or restarted, the
Data in MEMORY tables is lost.

But my tables created with ENGINES = MEMORY were not deleted when restarting the MySQL server.

Existing user deleted items in a database

I'm creating a web application where users have their own topics. Since topics are recorded for reporting purposes, it is important that previously used topics are not deleted so that they can be referenced in future reports.

In my relational database, topics are assigned to users via a user identification, I want users not to delete a topic, but to orphan by setting it user identification to zero, In this way, the topic can be referenced in reports by ID, but it is deleted from the user's perspective.

Is this a good practice? Should I move the topics to one instead? Deleted_Topics Table?

ubuntu 18.04 – Samba Recycle Bin – files are not deleted

I am using a Samba file share on Ubuntu 18.04 and have configured a recycle bin in the Samba configuration file. If I use the Windows File Explorer to navigate to file sharing and delete something, it will be moved to the trash as expected.

The problem occurs when I want to empty the trash. When I click in the trash folder and delete the contents, a trash folder is created in the trash and the content is moved there. I can never clear the trash.

My /etc/samba/smb.conf file is:


; workgroup = WORKGROUP
server string = file server
Security = user

  comment = public anonymous access
path = / srv /
searchable = yes
Create mask = 0660
Directory mask = 0771
writable = yes
Guest ok = yes
#Recycle Bin
vfs objects = recycle
recycle: repository = / srv / RecycleBin
recycle: keeptree = yes
recycle: versions = yes
recycle: exclude = * .tmp, *. temp

Is there a way Samba can allow the contents of the Recycle Bin to be deleted without recycling it?

16.04 – A logical volume has been deleted to free up space. Ubuntu is still looking for it at boot time. Do you need help?

While trying to free up space on my home media server, I deleted a logical volume from a Raid 5 array (MDADM). Now Ubuntu can not be loaded at boot time due to a timed mount of the deleted LV.

Running Ubuntu Server 16.04

There is another LV in the same volume group that is ok.

In recovery mode, everything is properly loaded and loaded (including the other LVs that are in the same VG). An attempt is then made to load the previously deleted logical volume (backup) and it times out, causing the boot process to fail. Failure.

I am then put into the "recovery mode", which is then immediately interrupted and the message "Welcome to emergency mode!"

Finally, when I scroll through the results of journalctl -xb, I see the following:

June 13 19:09:05 ubuntunas kernel: EXT4-fs (dm-2): file system mounted with ordered data mode. Options: (null)
June 13 19:09:05 ubuntunas systemd[1]: dev-DataVolume-Backup.device: Job dev-DataVolume-Backup.device / start has expired.
June 13 19:09:05 ubuntunas systemd[1]: Waiting time on device dev-Dataolume-Backup.device expired.
–Subject: Unit dev-DataVolume-Backup.device failed
–Defined-by: systemd

There are a variety of other messages that imply that loading this LV is a "dependency" …

Any suggestions for correction? I'm not very strong technically, so I really appreciate any help.

Many Thanks!